3 ms·
Since these questions will inevitably come up: - You fsync yourself to ensure durability. I can't see at a glance what fsync settings are used for the
by knightni 14y ago
Since these questions will inevitably come up:
- You fsync yourself to ensure durability. I can't see at a glance
what fsync settings are used for the speed tests.
- It's not transactional, although single operations are atomic.
- Indexes operate on a single-writer, multiple reader basis.
- No traditional joins, although you can of course write
a procedural function that joins for you.
- 3amOpsGuy 14y agoThese have come to be common features of NoSQL in general. I wouldn't be too surprised to see them here in a product marketed as NoSQL. The other attributes i'm not too fussed about personally, i figure i can always work around them or face the question "am i using the right tool for this job?" but the fsync one still gives me the heeby-jeebies (even though it's never bitten me despite many many TBs of data). Cassandra does periodic fsync's (although it can be configured). I understand HBase and Mongo have similar shennanigans.