{"action":"created","issue":{"url":"https://api.github.com/repos/mrniko/redisson/issues/202","labels_url":"https://api.github.com/repos/mrniko/redisson/issues/202/labels{/name}","comments_url":"https://api.github.com/repos/mrniko/redisson/issues/202/comments","events_url":"https://api.github.com/repos/mrniko/redisson/issues/202/events","html_url":"https://github.com/mrniko/redisson/issues/202","id":98350553,"number":202,"title":"Infinispan redis integration","user":{"login":"spaulg","id":206877,"avatar_url":"https://avatars.githubusercontent.com/u/206877?v=3","gravatar_id":"","url":"https://api.github.com/users/spaulg","html_url":"https://github.com/spaulg","followers_url":"https://api.github.com/users/spaulg/followers","following_url":"https://api.github.com/users/spaulg/following{/other_user}","gists_url":"https://api.github.com/users/spaulg/gists{/gist_id}","starred_url":"https://api.github.com/users/spaulg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spaulg/subscriptions","organizations_url":"https://api.github.com/users/spaulg/orgs","repos_url":"https://api.github.com/users/spaulg/repos","events_url":"https://api.github.com/users/spaulg/events{/privacy}","received_events_url":"https://api.github.com/users/spaulg/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mrniko/redisson/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-31T09:16:44Z","updated_at":"2015-08-03T08:23:24Z","closed_at":null,"body":"I'm contributing a redis integration to infinispan and am investigating the use of Redisson to use as the client.\r\n\r\nI need an efficient way to retrieve a list of all keys and iterate over them for processing, but because Redis can store millions of records, I wanted to avoid a list/queue of data pulled from the Redis server and held in memory on the client as this could wind up exhausting resources on the client.\r\n\r\nWill getBuckets, findKeysByPattern or findKeysByPatternAsync retrieve the keys in an efficient manor, like a database cursor stepping over each record, or is there another approach that is recommended to efficiently cater for this?"},"comment":{"url":"https://api.github.com/repos/mrniko/redisson/issues/comments/127162056","html_url":"https://github.com/mrniko/redisson/issues/202#issuecomment-127162056","issue_url":"https://api.github.com/repos/mrniko/redisson/issues/202","id":127162056,"user":{"login":"mrniko","id":1104661,"avatar_url":"https://avatars.githubusercontent.com/u/1104661?v=3","gravatar_id":"","url":"https://api.github.com/users/mrniko","html_url":"https://github.com/mrniko","followers_url":"https://api.github.com/users/mrniko/followers","following_url":"https://api.github.com/users/mrniko/following{/other_user}","gists_url":"https://api.github.com/users/mrniko/gists{/gist_id}","starred_url":"https://api.github.com/users/mrniko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrniko/subscriptions","organizations_url":"https://api.github.com/users/mrniko/orgs","repos_url":"https://api.github.com/users/mrniko/repos","events_url":"https://api.github.com/users/mrniko/events{/privacy}","received_events_url":"https://api.github.com/users/mrniko/received_events","type":"User","site_admin":false},"created_at":"2015-08-03T08:23:24Z","updated_at":"2015-08-03T08:23:24Z","body":"> I presume it blocks the connection at a low level until the callback processes items in a fixed sized queue on the client\r\n\r\nBut it's not atomic way. I mean there is a new keys could be created while you iterate your old keys."}}