-
Notifications
You must be signed in to change notification settings - Fork 233
Data Ingestion
Hongzheng Shi edited this page Dec 3, 2018
·
2 revisions
Data ingestions are achieved via upsert batches with the following procedures:
- Client contacts the server for schema resolution before preparing an upsert batches. This converts column names to column IDs.
- Client contacts the server for auto-enum value resolution. This converts all string values of auto-enum columns to integers. In distributed setup all servers need to agree on the same schema and auto-enum dictionary.
- Client prepares an upsert batch using the serialized format. Unlike a SQL insert, AresDB does not provide transaction atomicity and isolation higher than record level.