NoSQL

NoSQL Data Stores

 MongoDB ( C++) - document database
CouchDB - document database(key/value )
Cassandra - Column based , no single point of failure(Dynamo Architecture), Data modeling is based on Google Big Table.

Hbase ( Java )  - Google BigTable based architecture, Column Oriented distributed database on top of HDFS ( non distributed version works on local filesystem also , but distributed is only supported on HDFS).  See cassandra-vs-hbase for differences between Cassandra vs. Hbase.  High availability(No single point of failure-almost 100% uptime) , high number of reads/writes and if read/write consistency is not big issue Cassandra is wins. If Read/Write consistency is important and also if you need to query(read) large amount of data and extract small amount of result out of it Hbase wins.  Cassandra includes data storage and management both while Hbase is only for data management. For most of other activities, it relies on external services like HDFS, ZooKeeper etc.  In fact it does not have a query language, while Cassandra does.

Neo4j,OrientDB - Graph based, for handling complex relations/connections, for modeling classification

MemcacheDB, Redis - key/value based distributed caching.



 MongoDB document field renaming

Had to find all the documents which have a certain  embedded document and rename the field in the embedded documents.

db.user.find({"filed1.field2": {$exists:true}})
db.user.update( {"field1.field2":{$exists:true}},{ $rename: { "field1.field2":"field1.newfield2"}},{multi:true})

to find collections where field2 inside field1 has a particular "value".

db.user.find( { "field1.field2" : "value" } );



Comments

Post a Comment

Popular posts from this blog

SQL

Joins - Not always very obvious ( Following example uses Hive ). create table x_temp ( name string, p_date int  ) insert into x_temp(name,p_date) values ('x1',20181025),('x2', 20181026), ('x3',20181027) create table y_temp ( name string, s_date int  ) insert into y_temp(name,s_date) values ('x1',20181025),('x2', 20181026), ('x3',20181027) create table z_temp ( name string, p_date int, s_date int ) insert into z_temp(name,p_date,s_date) values ('z1','20181025','20181025') select x.*, y.* from x_temp x, y_temp y, z_temp z  where x.p_date != z.p_date and  y.s_date != z.s_date) generates 4 records... x.name,x.p_date,y.name,y.s_date x2, 20181026, x2, 20181026 x3, 20181027, x2, 20181026 x2, 20181026, x3, 20181027 x3, 20181027, x3, 20181027 select x.*, y.* from x_temp x, y_temp y, z_temp z  where x.p_date != z.p_date or  y.s_date != z.s_date) generates 8 records x.name,x.p_date,y.
Read more

Analytics

Types of Analytics ( Notes from AWS Course )  Descriptive - What happened ?  hindsight  Diagnostic - Why did it  happen?  hindsight & insight  Predictive  - What will happen ? insight & foresight  Prescriptive - What should I do ? foresight  Cognitive & AI  - What are recommended actions ? foresight & hypothesis input  Popular BI Tools:  https://www.cio.com/article/3284415/10-bi-tools-for-data-visualization.html
Read more

HIVE

1. When doing multi table joins, except the last ( right most ) table, other tables are buffered in the reducers. So to have less memory footprint on reducers, largest tables should be the last one as it is not buffered but streamed to reducers.   For Impala , it is different. 2.  You can filter the unwanted records within the join itself. SELECT  a.*,   b. * FROM a LEFT OUTER JOIN b ON ( a.key=b.key  AND  b.name= 'Tim'   AND a .name= 'Kim' ) 3. Joins are left associative. So execution happens from left to right and the result of joins is  fed into next join operation. 4. To find the value of variable     set hive.execution.engine 5. To find values of all variables set  6. If you want to pass different hive configuration settings in hive shell, you can use --hiveconf. For example hive --hiveconf hivi.optimize.sort.dynamic.partition=true --hiveconf hive.exec.dynamic.partition.mode=nonstrict 7.  In case you accidentally drop the p
Read more