schema on read and Schema on write

Schema on read  and Schema on write

Schema on Read :  Write your data first, figure out what it is later. 


Hive (in some cases), Hadoop, and many other NoSQL systems in general are about "schema on read" -- the schema is applied as the data is being read off of the data store

Benefits of schema on read:

• Flexibility in defining how your data is interpreted at load time
  • This gives you the ability to evolve your "schema" as time goes on
  • This allows you to have different versions of your "schema"
  • This allows the original source data format to change without having to consolidate to one data format
• You get to keep your original data
• You can load your data before you know what to do with it (so you don't drop it on the ground)
• Gives you flexibility in being able to store unstructured, unclean, and/or unorganized data

Downsides of schema on read:

• Generally it is less efficient because you have to reparse and reinterpret the data every time (this can be expensive with formats like XML)
• The data is not self-documenting (i.e., you can't look at a schema to figure out what the data is)
• More error prone and your analytics have to account for dirty data

Schema on write : Figure out what your data is first, then write it after.

A traditional relational database stores the data with schema in mind. It knows that the second column is an integer, it knows that it has 40 columns, etc. Therefore, you need to specify your schema ahead of time and have it well planned out. This is "schema on write" -- that is, the schema is applied when the data is being written to the data store.

Benefits of schema on write:

• Better type safety and data cleansing done for the data at rest
• Typically more efficient (storage size and computationally) since the data is already parsed

Downsides of schema on write:

• You have to plan ahead of time what your schema is before you store the data (i.e., you have to do ETL)
• Typically you throw away the original data, which could be bad if you have a bug in your ingest process
• It's harder to have different views of the same data