4 ms·
What's the indexing story? Do it yourself? "Any JSON store implementation will contain a half-specified bug-ridden implementation of half of Postgres's GIN/GiST
by floatboth 10y ago
What's the indexing story? Do it yourself? "Any JSON store implementation will contain a half-specified bug-ridden implementation of half of Postgres's GIN/GiST for jsonb"? :D
- dvirsky 10y agoWe're also developing a secondary indexing module (https://github.com/RedisLabsModules/secondary https://github.com/RedisLabsModules/secondary) and a search module (https://github.com/RedisLabsModules/RediSearch https://github.com/RedisLabsModules/RediSearch), the direction is to integrate one of them into the JSON module.
- traviscj 10y agoWise words -- a good set of indices are the first thing you need for real problems with realistic data sizes.
- dvirsky 10y agoRight now the problem that ReJSON tries to solve is very specific and typical for Redis users: You save JSON blobs on Redis (usually session data), now you want to get just a part of a JSON key, or manipulate just one element in a specific key. Until now you couldn't do it without loading the entire object into memory. ReJSON just allows you to manipulate that object or retrieve just a part of it efficiently. For this use case we do not need and will never need indexing.
- detaro 10y agoBy that logic, redis in general would not be useful for "real problems", whatever that is.
- weego 10y agoIt's Redis...