Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Calling AerospikeClient.get(Policy policy, Key[] keys) never returns / blocks forever #11

Closed
SimonChong opened this issue Sep 24, 2014 · 3 comments
Closed

Calling AerospikeClient.get(Policy policy, Key[] keys) never returns / blocks forever #11

SimonChong opened this issue Sep 24, 2014 · 3 comments

Comments

@SimonChong
Copy link

Calling AerospikeClient.get(Policy policy, Key[] keys) never returns WHEN an EMPTY ARRAY of keys is specified. It blocks forever and never comes back.

This should either throw an exception or return instantly with an empty Array or Records.
@BrianNichols
Copy link
Member

This will be fixed in the next release.

@SimonChong
Copy link
Author

That'll be great. I'm already finding the 3.0.29 fixes useful. Although it would be nice if the Vagrant machine was updated (to the new version of AS) as well ;)

Thanks.

@BrianNichols
Copy link
Member

Fixed in 3.0.30.

BrianNichols added a commit that referenced this issue Jun 27, 2015
@BrianNichols
Merge pull request #11 from citrusleaf/duplicate_nodeid
b2a889b 
AER-3648- Fix for duplicate node-id bug in client side
ijusti pushed a commit to ijusti/aerospike-client-java that referenced this issue Mar 28, 2023
Merge pull request aerospike#11 from mzhangsfly/query_update
ed1e752 
Query update
ijusti pushed a commit to ijusti/aerospike-client-java that referenced this issue Mar 28, 2023
@mzhangsfly
Merge pull request aerospike#11 from Playtika/feature/update-readme
130c8dc 
Update readme with actual version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SimonChong @BrianNichols