07:24:24 GMT ellistaa: SCAN, but using that should be avoided 07:24:43 GMT well, iterates the keys, not values 07:25:00 GMT minus: i read it should be avoided 07:25:03 GMT but it didnt say why 07:25:05 GMT minus: 07:25:33 GMT it's an O(n) operation with N being the number of keys in the DB 07:25:36 GMT if i ran scan i could get the list of keys then use it to look up all the keys/values 07:25:55 GMT yep 07:26:09 GMT minus: yeah … but i need to iterate over all the key values 07:26:21 GMT is there any other way? 07:27:14 GMT well, there's KEYS, but that's worse than SCAN in a way 07:27:51 GMT if you tell me what you want to achieve i can maybe give you an idea how to solve it differently 07:28:58 GMT minus: so im using cassandra as my db 07:29:19 GMT and for pictures im storing the like count 07:29:43 GMT but basically i can’t increment the field in cassandra 07:30:09 GMT so im doing it in redis, since redis is sync, and then im going to take all the data in redis and go update cassandraz 07:30:58 GMT i see 07:31:03 GMT the reason why i can’t just use a counter type in cassandra is because there are like 30 possible columns that can get incremented 07:31:22 GMT and cassandra requires all fields besides the counter be used in the primary key 07:31:23 GMT the updates to cassandra happen periodically? 07:31:41 GMT so i was going to update cassandra once every night 07:31:44 GMT at like 2 am 07:33:26 GMT SCAN + MGETs sound not too bad then 07:33:46 GMT ok cool 07:33:52 GMT what does MGET do 07:33:56 GMT i can look it up 07:34:06 GMT it's like GET, but you can query multiple things at once 07:34:12 GMT oh cool 07:34:22 GMT so scan will return all the keys? 07:34:47 GMT the other option would be to track all changed keys and updating those, but if you have massive amounts of changes that's probably slower 07:35:15 GMT “Since these commands allow for incremental iteration, returning only a small number of elements per call, they can be used in production without the downside of commands like KEYS or SMEMBERS that may block the server for a long time (even several seconds) when called against big collections of keys or elements.” 07:35:27 GMT so is that saying i can request like 200 keys at a time? 07:35:39 GMT yep 07:35:43 GMT oh cool 07:35:56 GMT be warned though: it's not atomic 07:36:15 GMT you could miss keys that change meanwhile 07:37:07 GMT minus: oh … i was going to wait until im done updating redis to call SCAN 07:37:12 GMT that should be fine right? 07:37:54 GMT you intend to pause writing to redis while you save to cassandra? well, that works of course 07:38:28 GMT so im going to read data from SQS, process the data which involves writing to redis, then after thats done, SCAN and update cassandra 07:38:51 GMT i really appreciate the clarification and help 07:39:05 GMT going to sleep 07:39:09 GMT ah, so no live system, just processing 07:39:17 GMT yeah no live systems 07:39:21 GMT you're welcome, good night 10:05:10 GMT Hello 10:05:54 GMT I am new on redis and I would like to write my very first function with set and get but I have not see on any documentation how to destoy data after X seconds like we do in memcached 10:05:59 GMT please any idea? 10:06:16 GMT for example, I would like to set a data for X seconds in php 11:08:30 GMT really 11:08:37 GMT is this channel about pokemongo ? 11:28:39 GMT hello, someone can help me with installation to linux? 12:30:27 GMT tomer_: what is it 12:31:32 GMT tomer_: unpack and do "sudo make install" 13:17:57 GMT hey I've been trying to find an ORM for redis using node... I've done some reasearch but I was wondering if anyone could tell me if they have a preference for one ORM and why... for example if you've used Nohm or waterline, what did you like about it and what didn't you like about it 17:09:44 GMT hi guys.. any onn ? 17:11:25 GMT Lets suppose I have a lot of news data(title, description, date etc) how would I insert them in a redis list ? 17:38:34 GMT thank u for your help ;)