Skip to content

Conversation

@ptupitsyn
Copy link
Contributor

@ptupitsyn ptupitsyn commented Jun 27, 2022

Implement IgniteSet in Java thin client.

  • Identify sets by name and cacheId. Name alone is not enough, because target cache is determined by atomicity, cache mode, backups count, group name, etc. Passing cacheId is much simpler, and helps with affinity.
  • Differences from thick API:
    • Iterator is AutoCloseable. However, users only need to close it when it did not reach the end.
    • Compute APIs are out of scope (affinityCall, affinityRun).
    • ClientIgniteSet#pageSize controls batching.
    • ClientIgniteSet#serverKeepBinary controls server-side deserialization behavior for user classes.

@ptupitsyn ptupitsyn marked this pull request as ready for review June 27, 2022 19:39
@ptupitsyn ptupitsyn merged commit 5bef64c into apache:master Jun 28, 2022
@ptupitsyn ptupitsyn deleted the ignite-16897 branch June 28, 2022 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants