I've created documentation ticket for UUID type - [1].
Now about Timestamp type. Binary protocol specification only specifies
how the data type should be transmitted by the network. The purpose and
main requirements for the protocol is to be compact and fast, it is not
designed to be used by user
Hi Stepan,
1) About UUID...
UUID binary encoding must be defined in the Binary Protocol
specification
(https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-uuid-guid-)
So, it's the issue against the spec first.
Regarding the clients..
Python client uses Python UUID
Hello again
Starting to check compatibility between thin clients in java/c++ and
py/php/nodejs and met some problems
1) Found that UUID mixed in a strange way if we taken it from Java/C++ to
PY/PHP/JS client and backwards
Have issue about it https://issues.apache.org/jira/browse/IGNITE-10691,
ple
Hi Stepan,
pls check the Ignite cfg you use - see the comments in the jira.
Also, the examples executors (including AuthTlsExample) are included
into NodeJS test suite in TeamCity which run periodically and
successfully passed. Eg. the latest one:
https://ci.ignite.apache.org/viewLog.html?bui
Hello again
If NodeJS sources found that example AuthTlsExample.js throwing exception
during execution
Output and grid configuration in
https://issues.apache.org/jira/browse/IGNITE-10447
Can someone have a look at it?
вс, 25 нояб. 2018 г. в 19:11, Stepan Pilschikov :
> My bad,
> You right
>
> в
My bad,
You right
вс, 25 нояб. 2018 г. в 05:37, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> AFAIK Map type did always behave correctly on client side, as it does
> now. This is a corresponding piece of my test suite:
>
> ```
> def test_put_get_map(client):
>
> cache = c
Stepan,
AFAIK Map type did always behave correctly on client side, as it does
now. This is a corresponding piece of my test suite:
```
def test_put_get_map(client):
cache = client.get_or_create_cache('test_map_cache')
cache.put(
'test_map',
(
MapObject.HAS
Dmitry,
Great, checked, now all things woks well
Hope that Igor made review for this PR
But what about Maps? Looks like different ticket? or it can be done in same
ticket scope?
пт, 23 нояб. 2018 г. в 23:58, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> Sorry, I forgot to up
Stepan,
Sorry, I forgot to update from upstream prior to start working on this
issue, and thus brought a regression. My bad. Just merged with the
latest master. Please, check it out again.
Dmitry
On 11/24/18 1:37 AM, Stepan Pilschikov wrote:
Dmitry,
Iv checked and its actually work
But a s
Dmitry,
Iv checked and its actually work
But a specially in this branch i found another bug
Please look at my last comment:
https://issues.apache.org/jira/browse/IGNITE-10358?focusedCommentId=16697285&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16697285
пт, 23
Stepan,
Thank you for your great job in evaluating Python thin client, as well
as other thin clients.
There was indeed a bug in Python client regarding the handling of type
hints in Collection type. I created a fix and did a PR under
IGNITE-10358 task, but the same PR is also fixes the probl
Dmitry, Alexey
Thank you for help, this answers help me a lot with understanding how
clients are work
Not so long time ago i met problem which is have expected behavior, but its
may broke some workflows in future for some users
Its all about not specified data types in collections and map's
All
Stepan!
TL/DR: what you got with Python client in your gist is an intended behavior.
Explanation: As per docs, Object array contains of type ID (which is
defaults to -1) and an array of objects.
https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-object-array
Your
Oh, now i finally understand (PHP and JS). And more, just found tests with
usage example (don't now why im just missed it)
Thank you
Waiting for Dmitry
пт, 26 окт. 2018 г. в 18:00, Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com>:
> thanks, now it's clear.
>
> For NodeJs and PHP clients:
>
thanks, now it's clear.
For NodeJs and PHP clients:
You cannot use OBJECT_ARRAY constant to specify a field type. This is
true for all non-primitive types. That's why you get ""type" argument
has incorrect value" exception.
Non-primitive types can be specified using special objects. In this
No
Now tried
code and output -
https://gist.github.com/pilshchikov/4c02057e624baa54326a1e75b4ee3f46
And it looks like it works
пт, 26 окт. 2018 г. в 17:10, Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com>:
> Hi Stepan,
>
> Have you tried the same with Java and .net thin clients as well and
> e
Hi Stepan,
Have you tried the same with Java and .net thin clients as well and
everything work fine?
Thanks,
-Alexey
26.10.2018 16:57, Stepan Pilschikov пишет:
Hi, everyone
Create new thread to centralize cross compatibility and others common
problems between thin clients
Tying to use Ob
Hi, everyone
Create new thread to centralize cross compatibility and others common
problems between thin clients
Tying to use Object array to exchange different data between JS, PHP and
Python thin clients
JS and PHP simply can't put any type of arrays
Python can put data, but if you take it, da
18 matches
Mail list logo
