Hi Igor,
in the newer version (will be available soon) getValues() is changed to
getValue() which gives sequential per-element access.
The API spec and the setup/run instructions are available with every
version.
Thanks,
-Alexey
08.05.2018 15:14, Igor Sapego пишет:
Hi, Pavel,
I took a lo
Hi, Pavel,
I took a look, and everything looks OK to me (except for the
lack of documentation, but I guess, this is expected for the
early version).
I have a question regardless Cursor class though. Other thin
clients, as far as I know, implement Cursor as a simple
iterator, which gives sequentia
Hi Denis,
Thank you for looking at the proposal and raising these questions! We'll
take them to discuss offline and will address your recommendations in the
next revision.
I will let Vladimir comment on the QueryEntity here though to make sure we
are on the same page.
Thanks,
P.
On Thu, Apr 1
Hello Pavel,
Thanks for the update. Haven't heard from you guys for a while but seems
you were too busy polishing the client. Looks great!
Please consider several questions/notes:
- Do we really want to migrate QueryEntity API [1] to Node.JS client? I
heard we planned to deprecate it in th
Igniters,
Just to give you an update on the next iteration of the Ignite Node.js thin
client implementation.
The second iteration is available for review/testing.
The changes are available in the pull request [1] or directly from our
repository [2].
The short README file [3] covers:
- the list
