Scribd
Upload
19 views2 pages

Module 3-1

Uploaded by

madhavan090603
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views2 pages

Module 3-1

Uploaded by

madhavan090603
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Comparison with Hive and Traditional database

Hive Traditional database

Schema on READ – it’s does not verify the Schema on WRITE – table schema is
schema while it’s loaded the data enforced at data load time i.e if the data
being loaded does not conformed on
schema in that case it will reject

It’s very easily scalable at low cost Not much Scalable, costly scale up.

It’s based on hadoop notation that is Write In traditional database we can read and
once and read many times write many time

Record level updates is not possible in Hive Record level updates, insertions and
deletes, transactions and indexes are
possible

OLTP (On-line Transaction Processing) is Both OLTP (On-line Transaction


not yet supported in Hive but it’s supported Processing) and OLAP (On-line Analytical
OLAP (On-line Analytical Processing) Processing) are supported in RDBMS

You might also like