61–69 of 69 posts
Earlier quoted context omitted.
"without pretending we are going to save the world". I felt a great disturbance in SV, as if millions of voices suddenly cried out in terror and were suddenly silenced.
This. You just made my day.
Earlier quoted context omitted.
Geo is insanely useful when you're after stuff within x miles of a known location - so a lot of mobile apps. My problem with many existing geo implementations is they assume that a circular radius is the query type I care about, and longitude and latitude is sufficient to know where I actually am in terms of jurisdiction, etc. Being able to add fine grained polygons to represent national, state, county or town bounda…
Hey Paul, we have this feature added as a Lua script, but adding it in a native way could be interesting actually. Itamar Haber wrote the Lua script and was pushing for adding it in a native way, I wanted to check after the release the actual demand for it.
Earlier quoted context omitted.
Geo is insanely useful when you're after stuff within x miles of a known location - so a lot of mobile apps. My problem with many existing geo implementations is they assume that a circular radius is the query type I care about, and longitude and latitude is sufficient to know where I actually am in terms of jurisdiction, etc. Being able to add fine grained polygons to represent national, state, county or town bounda…
Hey Paul, we have this feature added as a Lua script, but adding it in a native way could be interesting actually. Itamar Haber wrote the Lua script and was pushing for adding it in a native way, I wanted to check after the release the actual demand for it.
UPDATE: found it https://github.com/RedisLabs/geo.lua
The geo API seems rather... specific. Is there really a demand for it?
Geo is insanely useful when you're after stuff within x miles of a known location - so a lot of mobile apps. My problem with many existing geo implementations is they assume that a circular radius is the query type I care about, and longitude and latitude is sufficient to know where I actually am in terms of jurisdiction, etc. Being able to add fine grained polygons to represent national, state, county or town bounda…
Would something like that work for you? What kind of numbers of points and polygons are you looking at and how quickly do you need to solve the problem?
The new BITFIELD seems like it could be really cool, but I can't quite figure out the use case. Anybody planning on using that that can enlighten me? Thanks.
I plan on using it to track what database objects have a corresponding cached image thumbnail. 10 million objects in my database, thumbnails generated on the fly, fast get/set the unique ID of the object in the bitfield. very small storage for what you get.
From what I read, BITFIELD behaves differently -- it treats your data as a series of "packed" bits. So while with BITSET you operate on each bit individually, with BITFIELD you operate on a series of bits with a starting offset, and you have to be mindful of the length.
The geo API seems rather... specific. Is there really a demand for it?
On my wish list would be adding a bounding box query to return results within a map displayed on the current screen: e.g.: https://www.algolia.com/doc/javascript#search__inside-boundi... or e.g.: http://postgis.refractions.net/docs/ST_MakeEnvelope.html
Earlier quoted context omitted.
Thanks, I really receive good sentiments from the community. I've the feeling that this is not due just to the fact that many developers find Redis useful. It has very serious limits like many other softwares. It is that so far Redis was never proposed as "The Shit", the silver bullet that will save you from your data problem. Is just something I and the other contribs try to do with love, without pretending we are g…
This is it. Redis is one of the few things in the data-persistence space that is honest about what it can't do. So many other DBs, caches, or whatever will promise that they can solve all my problems, making me quite angry when I spend weeks developing around them and find out that I've just wasted all that time because their marketing people lied to me.
Earlier quoted context omitted.
This is it. Redis is one of the few things in the data-persistence space that is honest about what it can't do. So many other DBs, caches, or whatever will promise that they can solve all my problems, making me quite angry when I spend weeks developing around them and find out that I've just wasted all that time because their marketing people lied to me.
I'm curious: other than the obvious (MongoDB) what are the other offenders?
Riak 1.x. Anyone remember Riak Search? Not the one in 2.x that offloads it to Solr (I don't know if that actually works), but the one before that, the one they deprecated before there was anything to replace it with.
Any database that promises that you can solve your problems with MapReduce. The developers do not actually want you to MapReduce inside their database. It will probably stall your database so hard it makes it unavailable. Their sales people made them put it on the feature checklist.