NoSQL

2013/05/21 -- Faraaz Sareshwala
2013/05/21 -- Faraaz Sareshwala
about 1 hour ago
2013/05/21 -- Arthur Zubarev
2013/05/21 -- Arthur Zubarev
about 2 hours ago
Geo data can be stored either as an array such as [ 55.5, 42.3 ] or embedded documents such as { lng : 55.5 , lat : 42.3 }. For the embedded document, do the property names have to be "lat" and "lng"? Also, there is talk of a "legacy ...
Geo data can be stored either as an array such as [ 55.5, 42.3 ] or embedded documents such as { lng : 55.5 , lat : 42.3 }. For the embedded document, do the property names have to be "lat" and "lng"? Also, there is talk of a "legacy coordinate pair", which I do not understand. Is that a separate format from either of these?
about 2 hours ago
2013/05/21 -- Arthur Zubarev
2013/05/21 -- Arthur Zubarev
about 3 hours ago
I have a busy collection with almost a billion documents and would like to remove() half of them, but calling remove() on the replica set primary is painful. I'd like to use an offline slave this like: 1. Restart a secondary serv...
I have a busy collection with almost a billion documents and would like to remove() half of them, but calling remove() on the replica set primary is painful. I'd like to use an offline slave this like: 1. Restart a secondary server in standalone 2. Remove many documents (or select the documents to keep into a new
about 4 hours ago
I am using CDH4 mongo hadoop connector and I got unauthorized exception: org.apache.pig.backend.executi onengine.ExecException: ERROR 2118: Unable to calculate input splits: unauthorized at org.apache.pig.backend.hadoop. executioneng...
I am using CDH4 mongo hadoop connector and I got unauthorized exception: org.apache.pig.backend.executi onengine.ExecException: ERROR 2118: Unable to calculate input splits: unauthorized at org.apache.pig.backend.hadoop. executionengine.mapReduceLayer .PigInputFormat.getSplits(PigI nputFormat.java:288)
about 5 hours ago
We have a use case where we'd like to run a map reduce job every couple of hours, but we're finding that when the job enters the "M/R Reduce Post Processing" stage the global lock hits 100% rendering the MongoDB instance on th...
We have a use case where we'd like to run a map reduce job every couple of hours, but we're finding that when the job enters the "M/R Reduce Post Processing" stage the global lock hits 100% rendering the MongoDB instance on this machine virtually useless. We're reducing the output to an already existing collection which resides
about 5 hours ago
2013/05/20 -- Ilya Kirnos
2013/05/20 -- Ilya Kirnos
about 6 hours ago
2013/05/20 -- Edward Capriolo
2013/05/20 -- Edward Capriolo
about 7 hours ago
2013/05/20 -- Arthur Zubarev
2013/05/20 -- Arthur Zubarev
about 8 hours ago