Re: [Discussion] Race on heartbeat update in checkpoint thread

2021-07-20 Thread Ivan Daschinsky
+1 For current fix. Code is clean and understandable. I suppose that the current fix is a correct variant to update heartbeatTs. вт, 20 июл. 2021 г. в 16:13, Alex Plehanov : > Hello, Ilya > > > But anyway, I propose to remove the update of the heartbeat from other > threads altogether and wrap

Re: [DISCUSS] Confuse default inspections.

2021-07-20 Thread Ivan Daschinsky
Hi! Firstly, lets talk about interfaces. 1. First of all, do we have an automatic inspection for it? AFAIK we don't 2. I am for consistency. At least for production code. Nothing worse is when someone mixes both approaches. About a prohibition of curly brackets around one line -- I am strongly

[ANNOUNCE] Release pyignite-0.5.1

2021-07-20 Thread Ivan Daschinsky
Igniters! I suppose it is time to release pyignite 0.5.1. There are few good features available and some users are eager to try it. 1. Added ability to record clients' events by event listeners. This is a quite agile mechanism, and it allows writing custom metrics, tracing and debugging. 2.

Client events and monitoring in pyignite

2021-07-15 Thread Ivan Daschinsky
Hi, igniters! Recently, one user asked me to add this functionality to pyignite. Many users want: 1. To expose client metrics of app to prometheus (for example) 2. To write custom logic on specific client events (connect, disconnect, reconnect) 3. To perform tracing I suggests to introduce

Re: IEP-61 Transaction API desing for Ignite 3

2021-07-14 Thread Ivan Daschinsky
tent all table projections for better UX. > > Let's allow > > table.kvView().withTx(tx) > > to user may cache kvVew instance and do > > kvView.withTx(tx) > > rather than > > table.withTx(tx).kvVew() > > > > > > > > On Wed, J

Re: IEP-61 Transaction API desing for Ignite 3

2021-07-14 Thread Ivan Daschinsky
I as small as possible for now. > Anyway, these methods can be added later, if the need arises. > > > > > > ср, 14 июл. 2021 г. в 10:13, Ivan Daschinsky : > > > Alexey, and is there any analogue to close() of transaction? When you > start > > transaction, you shou

Re: IEP-61 Transaction API desing for Ignite 3

2021-07-14 Thread Ivan Daschinsky
Alexey, and is there any analogue to close() of transaction? When you start transaction, you should somehow to close it, if you don't catch exception or forget to commit. I suggest to add method closeAsync() to Transaction, so user can call it in handle or whenComplete, i.e. So code will looks

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-13 Thread Ivan Daschinsky
d be in core module > > > > > > > > > > It will be in a separate module (ignite-client). > > > > > I was talking about "core library" as a primary set of modules that > > we > > > > > ship. > > > > > Integrations with 3rd par

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-11 Thread Ivan Daschinsky
onomic and work everywhere. > > > On Sun, Jul 11, 2021 at 8:24 AM Ivan Daschinsky > wrote: > > > > But configuration should be a POJO - a class with setters and getters, > > nothing else. > > Why it should? Why ClientConfiguration should be serializable? W

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-11 Thread Ivan Daschinsky
. 2021 г., 17:48 Pavel Tupitsyn : > Serialization is just one example, and it does not have to be XML. > JSON, YAML, HOCON configs are widely used. > > Anyway, I see no reason for it NOT to be a POJO. > POJOs are ergonomic and work everywhere. > > > On Sun, Jul 11, 2021 at

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-10 Thread Ivan Daschinsky
e corresponding benefits, > like easy serialization. > WebClient.Builder is an interface that does not even provide a way to get > the property value back. > > > To be clear, I don't have strong opinions on naming (it can be > Ignition.start or IgniteClient.connect or whatever).

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-10 Thread Ivan Daschinsky
vide an example of that, a piece of code with suggested > API usage? Ideally compared to the current 2.x approach. > > On Sat, Jul 10, 2021 at 3:20 PM Ivan Daschinsky > wrote: > > > It is a quite questionable decision , as for me, to have specific static > > met

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-10 Thread Ivan Daschinsky
as a primary set of modules that we > > > ship. > > > Integrations with 3rd party libraries and frameworks can be shipped as > > > extensions. > > > > > > Anyway, let's postpone the discussion of Rx and Kotlin. > > > The main goal right now is to imple

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-09 Thread Ivan Daschinsky
pletableFuture. > > On Fri, Jul 9, 2021 at 1:31 PM Ivan Daschinsky > wrote: > > > You forget about reactive api :) > > > > And whats a problem with discocerability? > > > > var syncApi = client.sync(); > > syncApi.put(k, v); > > > > va

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-09 Thread Ivan Daschinsky
quot; and see a list of suggestions > like get, getAsync, getAndPut, getAndPutAsync. > I don't want to have a separate interface and a separate variable to deal > with sync and async methods. > > Not sure what's the problem with documentation - can you elaborate please? > > On Fri, Jul 9,

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-09 Thread Ivan Daschinsky
ootstrap.html > > > > 2021-07-09 1:41 GMT+03:00, Valentin Kulichenko < > > valentin.kuliche...@gmail.com>: > > > Ivan, > > > > > > I've seen the link, but I still don't understand what exactly you > propose > > > to change in

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-08 Thread Ivan Daschinsky
://www.baeldung.com/java-redis-lettuce чт, 8 июл. 2021 г., 23:47 Valentin Kulichenko : > Ivan, > > Can you please clarify what you mean by "separate creation of client and > connection"? Can you give an example? > > -Val > > On Thu, Jul 8, 2021 at 12:53 PM Ivan Daschinsky &g

Re: Ignite 3.0 Ignition API, node startup, and thin client startup

2021-07-08 Thread Ivan Daschinsky
I'm sorry, but why we didn't consider to separate creation of Client and connection? Why not to make async variant of connection? See for example [1] [1] --- https://lettuce.io/core/release/api/index.html чт, 8 июл. 2021 г., 09:50 Pavel Tupitsyn : > Val, > > So the plan is: > > - Remove

Re: Ignite 3.0 Tuple API: how to check if value is null?

2021-07-06 Thread Ivan Daschinsky
Valentin Kulichenko : > So what happens if the value is NULL? Exception? > > -Val > > On Tue, Jul 6, 2021 at 1:52 PM Ivan Daschinsky > wrote: > > > > Out of curiosity, what would this code do if the value is NULL? What is > > the > > type of the 'weight' va

Re: Ignite 3.0 Tuple API: how to check if value is null?

2021-07-06 Thread Ivan Daschinsky
ut of curiosity, what would this code do if the value is NULL? What is the > type of the 'weight' variable? > > if (tuple.TryGetFloatValue("weight", out var weight)) > doSomething(weight) > > -Val > > On Tue, Jul 6, 2021 at 2:13 AM Ivan Daschinsky > wrote: > &

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-06 Thread Ivan Daschinsky
> > as maps (String -> val). > > > > [1] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach#IEP54:SchemafirstApproach-Dynamicschemaexpansion(Live-schema) > > > > On Thu, Jul 1, 2021 at 8:31 PM Ivan Daschinsky > > wrote: &g

Re: Ignite 3.0 Tuple API: how to check if value is null?

2021-07-06 Thread Ivan Daschinsky
doSomething(tuple.floatValue("weight")) > > Whereas in other languages you could do it in one shot: > > if (tuple.TryGetFloatValue("weight", out var weight)) > doSomething(weight) > > or Option weight = tuple.floatValue("weight") and so on.

Re: Ignite 3.0 Tuple API: how to check if value is null?

2021-07-06 Thread Ivan Daschinsky
Sorry, but what is wrong with simple method isNull() вт, 6 июл. 2021 г., 09:55 Pavel Tupitsyn : > Val, > > > I don't think there is a significantly better way > > of doing this in Java. > > Yep looks like there is no way to return two values without boxing. > No ref, no out, no value types. > >

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
res > can be stored as blobs. So if you need a basic KV cache, you can always > create a table with two blob fields - one for key and one for value - and > store anything there. > > -Val > > On Thu, Jul 1, 2021 at 9:55 AM Ivan Daschinsky > wrote: > > > Val, am I right, t

Re: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Ivan Daschinsky
GNITE_SQL_MERGE_TABLE_MAX_SIZE) are OK to appear in the logs. > > -Val > > On Thu, Jul 1, 2021 at 9:47 AM Ivan Daschinsky > wrote: > > > We can add add an extra param in annotation, that blocks param to be > > printed, just set it to false by default and block it wh

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
ble > enough to allow other implementations for different languages and > platforms. > > -Val > > On Thu, Jul 1, 2021 at 9:38 AM Ivan Daschinsky > wrote: > > > Andrey, yep, you are right. This was just a quick idea. As for me, I just > > don't want to repeat

Re: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Ivan Daschinsky
s that is up to a discussion. > > > > -Val > > > > On Thu, Jul 1, 2021 at 9:29 AM Ivan Daschinsky > > wrote: > > > > > This is security through obscurity, an obvious and a well-known anti > > > pattern. I suppose that printing jvm options, that is registered

Re: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Ivan Daschinsky
. I would still go with opt-in rather > than opt-out though, but I guess that is up to a discussion. > > -Val > > On Thu, Jul 1, 2021 at 9:29 AM Ivan Daschinsky > wrote: > > > This is security through obscurity, an obvious and a well-known anti > > pa

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
e' VARCHAR DEFAULT "abc"; > ) > INSERT INTO t1 VALUES(1) > > Actually, this will add a row (1, "abc") > > Your suggestion related to missed fields will not work this way as it is > impossible to distinct > case with 'null' value from the case with a default value

Re: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Ivan Daschinsky
le ticket and prepare a PR. > > Please do not rush. Let's listen to other community members. This > question > > is about security and it should not be discussed in a hurry (even though > it > > looks like an obvious thing). > > > > Thanks, > > S. > > > >

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
Ivan, what are extra serde steps you are talking about? > > > > Best Regards, > > Igor > > > > > > On Thu, Jul 1, 2021 at 5:52 PM Ivan Daschinsky > > wrote: > > > > > > I agree. But this was decided before in IEP-54, and is out of scope > for

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
out? > > Best Regards, > Igor > > > On Thu, Jul 1, 2021 at 5:52 PM Ivan Daschinsky > wrote: > > > > I agree. But this was decided before in IEP-54, and is out of scope for > > current IEP. > > Would you like to start a separate thread to discuss this? O

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
чт, 1 июл. 2021 г., 17:50 Ivan Daschinsky : > > Here is the description of TUPLE_GET_ALL: > - UUID: table ID > - int: schema ID > - arr of arr: array of rows with values for all columns in given schema > > I suppose that we should describe this more verbose and explicit.

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
thread to discuss this? Or I can do this > a bit later. > > On Thu, Jul 1, 2021 at 4:41 PM Ivan Daschinsky > wrote: > > > > This is described in all operations that include multiple tuples. > > No it isn't, I have carefully read code and IEP, in your code you

Re: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Ivan Daschinsky
I suppose, that all normal users should not suffer from this restrictions. Nobody will pass password using jvm options. It is absolutely insane, normal users pass passwords using environment variables. At least, we could just hide params that match specific pattern Ilya, go ahead, file ticket

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
on. > > > > As for me, these excercises with schema's doesn't worth a lot > > I'll add a benchmark and we'll see. > > > On Thu, Jul 1, 2021 at 3:17 PM Ivan Daschinsky > wrote: > > > I suppose, that there is not neccesary to write schema versions in each > row

Re: Apache Ignite 2.11

2021-07-01 Thread Ivan Daschinsky
Binary prorocol description should stand and improved (there are some mistakes in this article) чт, 1 июл. 2021 г., 16:05 Ivan Daschinsky : > https://apache-ignite-binary-protocol-client.readthedocs.io/en/stable/ > > AFAIK, thin clients have been already removed since 2.10 > > чт

Re: Apache Ignite 2.11

2021-07-01 Thread Ivan Daschinsky
https://apache-ignite-binary-protocol-client.readthedocs.io/en/stable/ AFAIK, thin clients have been already removed since 2.10 чт, 1 июл. 2021 г., 15:57 Nikita Safonov : > Hi guys! > > Sorry, totally missed this email. > > I can do this right away. > > Just a couple of questions first: > > [1]

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
Pavel Tupitsyn : > Ivan, tuple serialization section added to the IEP, let me know if it is > clear enough. > > Thanks! > > On Thu, Jul 1, 2021 at 2:06 PM Ivan Daschinsky > wrote: > > > I can't find any description of tuple serialization in IEP, only in code > >

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
since it is the only > API that we have right now, as noted in Risks and Assumptions. > > On Thu, Jul 1, 2021 at 1:53 PM Ivan Daschinsky > wrote: > > > Also, is there any clear information about KV api? Is there any plan to > > implement it? Or is there any proposal about

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
Also, is there any clear information about KV api? Is there any plan to implement it? Or is there any proposal about it? чт, 1 июл. 2021 г., 13:51 Ivan Daschinsky : > Pavel, but IEP is in progress, isn't it? > > 1. There is not any information about tuple serialization. And there isn't

Re: IEP-76 Thin Client Protocol for Ignite 3.0

2021-07-01 Thread Ivan Daschinsky
Pavel, but IEP is in progress, isn't it? 1. There is not any information about tuple serialization. And there isn't a clear consensus about it. 2. There is not any information about schrma serialization format. And AFAIK, there isn't a clear consensus also. чт, 1 июл. 2021 г., 13:26 Pavel

Re: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Ivan Daschinsky
I suppose, that we should revert this particular line. I don't understand who ever considers vm options as sensitive info. ср, 30 июн. 2021 г., 22:52 Shishkov Ilya : > Hi Igniters, > > This feature [1, 2] prevents logging of the VM arguments when > IGNITE_TO_STRING_INCLUDE_SENSITIVE option is

Re: IGNITE-14812: Statistics

2021-06-23 Thread Ivan Daschinsky
AFAIK, it is enough to include mention of this library in NOTICE, please see here [1][2][3] [1] -- https://www.apache.org/legal/src-headers.html#3party [2] -- https://www.apache.org/legal/src-headers.html#notice [3] -- https://www.apache.org/legal/resolved.html ср, 23 июн. 2021 г. в 17:36,

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-23 Thread Ivan Daschinsky
г. в 14:07, Pavel Tupitsyn : > Igniters, > > Looks like there are no objections and we can accept the proposal. > I will close it tomorrow and move on to the thin client protocol itself. > > On Fri, Jun 18, 2021 at 12:10 PM Ivan Daschinsky > wrote: > > > >>

[ANNOUNCE] Apache IGNITE python thin client (pyignite) 0.5.0 released

2021-06-21 Thread Ivan Daschinsky
m here: https://dist.apache.org/repos/dist/release/ignite/pyignite/0.5.0/ Please let us know if you have any problems https://ignite.apache.org/community/resources.html#ask Regards, Ivan Daschinsky on behalf of the Apache Ignite community.

[RESULT] [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
Hello, Igniters! Release pyignite-0.5.0-rc1 has been accepted. The votes received: 3 "+1" binding votes 4 "+1" votes There are no "+0" or "-1" Here the votes received: - Igor Sapego (binding) +1 - Pavel Tupitsyn (binding) +1 - Nickolay Izhikov (bind

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
:08, Ivan Daschinsky : > >> we explicitly set use_ssl=True. > Sorry, typo -- implicitly > > пт, 18 июн. 2021 г. в 12:59, Ivan Daschinsky : > >> AHA! I see, this is not a bug -- this is a feature. If you pass username >> and password, we explicitly set

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
>> we explicitly set use_ssl=True. Sorry, typo -- implicitly пт, 18 июн. 2021 г. в 12:59, Ivan Daschinsky : > AHA! I see, this is not a bug -- this is a feature. If you pass username > and password, we explicitly set use_ssl=True. So if your cluster is > configu

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
And this behavior is thoroughly described in docs https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#password-authentication пт, 18 июн. 2021 г. в 12:59, Ivan Daschinsky : > AHA! I see, this is not a bug -- this is a feature. If you pass username > and pa

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
. Who wants authentication that sent without encryption? пт, 18 июн. 2021 г. в 12:54, Ivan Daschinsky : > Just rechecked test on release branch, add extra check with cluster > activation and putting some data -- everything works ok. Authentication > enabled, persistence enabled, > with and

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
Just rechecked test on release branch, add extra check with cluster activation and putting some data -- everything works ok. Authentication enabled, persistence enabled, with and without ssl. Could you please provide you ignite config and your code. пт, 18 июн. 2021 г. в 12:46, Ivan Daschinsky

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-18 Thread Ivan Daschinsky
gt; > >> Checked pip install from tar.gz on Python 3.8 on Ubuntu 20.04, ran some > of > >> the examples. > >> > >> On Thu, Jun 17, 2021 at 2:32 PM Igor Sapego wrote: > >> > >>> +1 from me > >>> > >>> Best Regards

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-18 Thread Ivan Daschinsky
not the implementation. > > Important takeaway is: > The format does not prevent someone from implementing it efficiently. > > > > [1] > > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryWriterExImpl.java#L

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
peration. > So, BO solution produces a lot of garbage and BO has noticable overhead > which affects the object footprint. > > чт, 17 июн. 2021 г., 21:41 Ivan Daschinsky : > > > >> Double checked -- there is not any links to PR either in IEP or in > jira > > issue

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
>> Double checked -- there is not any links to PR either in IEP or in jira issue Sorry, there is a link in IEP, but not in jira ticket. чт, 17 июн. 2021 г. в 21:39, Ivan Daschinsky : > Andrey, > >> arbitrary object graph > Also, that is not true, msgpack format doesn't h

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
Andrey, >> arbitrary object graph Also, that is not true, msgpack format doesn't handle circular graphs. Think about msgpack as binary json. You couldn't understand full structure of message if you didn't deserialize it fully before, maps and arrays are serialized just as contiguos chunks of

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
maful way" and "field names are not > included" in the same sentence. > > > On Thu, Jun 17, 2021 at 4:46 PM Ivan Daschinsky > wrote: > > > Also, it's well known use case of msgpack in the world of memory grids -- > > tarantool.io uses msgpack for clients

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
9/09/29/net-serialization-benchmark-2019-roundup/ > [2] https://github.com/apache/ignite/pull/9178 > > On Thu, Jun 17, 2021 at 4:02 PM Ivan Daschinsky > wrote: > > > Could you please share your code for benchmarks? > > > > чт, 17 июн. 2021 г. в 15:56, Ivan Daschinsk

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
Could you please share your code for benchmarks? чт, 17 июн. 2021 г. в 15:56, Ivan Daschinsky : > Hi, Pavel. Have you considered format with schema? Or schemaless of a > candidate format was a prerequisite? > As for me, msgpack is great, but I suppose that we should benchmark

Re: IEP-75 Thin Client MsgPack Serialization for 3.0

2021-06-17 Thread Ivan Daschinsky
Hi, Pavel. Have you considered format with schema? Or schemaless of a candidate format was a prerequisite? As for me, msgpack is great, but I suppose that we should benchmark formats thoroughly. And not only for Java. чт, 17 июн. 2021 г. в 15:29, Pavel Tupitsyn : > Igniters, > > I have drafted

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-17 Thread Ivan Daschinsky
voting period till June 18, 15:00 UTC ср, 16 июн. 2021 г. в 17:34, Ivan Daschinsky : > The vote will end at June, 17 15:00 UTC. > > ср, 16 июн. 2021 г. в 17:33, Ivan Daschinsky : > > > > Dear Igniters! > > > > Release candidate binaries for subj are uploaded and rea

Re: [DISCUSSION] Code style. Variable abbrevations

2021-06-17 Thread Ivan Daschinsky
I'm sorry, but the rule is not strict and, moreover, not clear enough for constans. See here [1] ``` Type and method names are usually not abbreviated (except for the well-accepted abbreviations such as EOF, Impl, Fifo, etc.). Abbreviation applies to local variables, method parameters, class

Re: [VOTE] Release pyignite 0.5.0-rc1

2021-06-16 Thread Ivan Daschinsky
The vote will end at June, 17 15:00 UTC. ср, 16 июн. 2021 г. в 17:33, Ivan Daschinsky : > > Dear Igniters! > > Release candidate binaries for subj are uploaded and ready for vote > You can find them here: > https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.0-rc1

[VOTE] Release pyignite 0.5.0-rc1

2021-06-16 Thread Ivan Daschinsky
Dear Igniters! Release candidate binaries for subj are uploaded and ready for vote You can find them here: https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.0-rc1 If you follow the link above, you will find source package (*.tar.gz and *.zip) and binary packages (wheels) for windows

[CANCEL][VOTE] Release pyignite 0.5.0-rc0

2021-06-16 Thread Ivan Daschinsky
This vote was canceled since it was decided to add [1] to the release. [1] has been already merged to master branch and cherrypicked to release branch. New vote will be created soon. [1] -- https://issues.apache.org/jira/browse/IGNITE-14911

Re: [VOTE] Release pyignite 0.5.0-rc0

2021-06-16 Thread Ivan Daschinsky
.5.0/ > > > > Everything looks good. > > > > Best Regards, > > Igor > > > > > > On Tue, Jun 15, 2021 at 10:09 PM Ivan Daschinsky > > wrote: > > > >> Also checked hash sums and signature. Packages are verified and > >> signatur

Re: Seconds and milliseconds confusion in python thin client

2021-06-16 Thread Ivan Daschinsky
, because it corresponds to socket.settimeout method in python (accepts floating point number) This is a compromise between usability and backward compatibility WDYT? ср, 16 июн. 2021 г. в 11:09, Ivan Daschinsky : > > I've created ticket for it https://issues.apache.org/jira/browse/IGNITE

Re: Seconds and milliseconds confusion in python thin client

2021-06-16 Thread Ivan Daschinsky
I've created ticket for it https://issues.apache.org/jira/browse/IGNITE-14911 ср, 16 июн. 2021 г. в 08:37, Ivan Daschinsky : > > Ops, i don't even know about it. I believe that this is so rarely used, i > don't even noticed it. I am talking about transactions and expiry policy. I

Re: Seconds and milliseconds confusion in python thin client

2021-06-15 Thread Ivan Daschinsky
I can see client.sql(timeout) in 0.4.0 for example, which is int number of > ms. > > Best Regards, > Igor > > > On Tue, Jun 15, 2021 at 11:52 PM Ivan Daschinsky > wrote: > > > BTW, common approach is to treat both ints and floats as seconds. Floats > > are use

Re: Seconds and milliseconds confusion in python thin client

2021-06-15 Thread Ivan Daschinsky
., 23:49 Ivan Daschinsky : > Igor, I suppose that you are probably right. But there is no need to > notice or deprecate something. This functionality is not released yet > > вт, 15 июн. 2021 г., 23:41 Igor Sapego : > >> Hi Igniters, >> >> I've noticed a weird behaviou

Re: Seconds and milliseconds confusion in python thin client

2021-06-15 Thread Ivan Daschinsky
Igor, I suppose that you are probably right. But there is no need to notice or deprecate something. This functionality is not released yet вт, 15 июн. 2021 г., 23:41 Igor Sapego : > Hi Igniters, > > I've noticed a weird behaviour of python thin client. In those places where > we have > timeouts

Re: [VOTE] Release pyignite 0.5.0-rc0

2021-06-15 Thread Ivan Daschinsky
/info/verification.html вт, 15 июн. 2021 г. в 22:01, Ivan Daschinsky : > > +1 From me > Checked building from source on Ubuntu 20.04 amd64 for pythons 3.6.12 > 3.7.9 3.8.6 3.9.1. > Checked installing binary packages on Ubuntu 20.04 amd64 and Windows > 10 amd 64 for pythons 3.6.12

Re: [VOTE] Release pyignite 0.5.0-rc0

2021-06-15 Thread Ivan Daschinsky
documentation for tag 0.5.0.rc0 on readthedocs.io вт, 15 июн. 2021 г. в 21:58, Ivan Daschinsky : > > Dear Igniters! > > Release candidate binaries for subj are uploaded and ready for vote > You can find them here: > https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.0-rc0 > >

Re: [DISCUSSION] Release python-0.5.0

2021-06-15 Thread Ivan Daschinsky
Ok, guys, code is freezed. RC is almost ready, the voting is going to start soon. Stay tuned. вт, 15 июн. 2021 г. в 10:35, Ivan Daschinsky : > > I've created release branch [1]. > > I suppose that since there is not any open issue related to python, > code freeze will be at 06/15

Re: [DISCUSSION] Release python-0.5.0

2021-06-15 Thread Ivan Daschinsky
I've created release branch [1]. I suppose that since there is not any open issue related to python, code freeze will be at 06/15/2021 12:00 UTC. [1] -- https://github.com/apache/ignite-python-thin-client/commits/pyignite-0.5.0 пт, 11 июн. 2021 г. в 17:29, Ivan Daschinsky : > > Since

Re: Apache Ignite 2.11

2021-06-11 Thread Ivan Daschinsky
I suppose that python thin client documentation should be removed, only link to actual readthedocs.io documentation should remain пт, 11 июн. 2021 г., 14:01 Игорь Гусев : > > Hello all. > > I’d also join in on Nikita’s question n what docs are required for > release. Currently we only have one

Re: [DISCUSSION] Release python-0.5.0

2021-06-11 Thread Ivan Daschinsky
Since nobody has any contradiction and all planned issues are merged to master, I am going to cut release branch next tuesday and to prepare release binaries for voting. Stay tuned. чт, 10 июн. 2021 г. в 09:54, Nikolay Izhikov : > > +1 > > > 9 июня 2021 г., в 09:48, Ivan Daschi

[DISCUSSION] Release python-0.5.0

2021-06-09 Thread Ivan Daschinsky
Hi, folks! I suppose, that it's time to release the next version of python thin client, because we are ready to ship new cool features. 1. Expiry policy (TTL) support (merged to master) [1] 2. Transactions (patch available) [2] 3. As part of tx api, huge performance improvement of asyncio [3] 4.

Re: [MTCGA]: new failures in builds [6024739] needs to be handled

2021-05-28 Thread Ivan Daschinsky
Hi, Pavel, could you please look at this [1]? It seems after updating TC, few new inspections arrived. ]1] -- https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetInspections/6024739?buildTab=Inspection пт, 28 мая 2021 г. в 04:55, : > > Hi Igniters, > > I've detected

Re: [DISCUSSION] Transactional cache could be in inconsistent state after node recovery.

2021-05-24 Thread Ivan Daschinsky
As for me, it is logical to remove this flag after merging IGNITE-6324. I suppose that the slowdown is negligible. BTW, yardstick reports contains no information about confidence interval. I suppose that another run could show not drop but improvement :) пн, 24 мая 2021 г. в 12:06, Zhenya

Re: Building with maven 3.8.1

2021-05-24 Thread Ivan Daschinsky
r. > I think it will be available with 2021.1 version that is going to be > delivered soon. > > > > On 21 May 2021, at 12:28, Ivan Daschinsky wrote: > > > > Hi. But where is TC run? And I suppose, that > > https://travis-ci.com/github/apache/ignite/jobs/5066755

Re: Building with maven 3.8.1

2021-05-21 Thread Ivan Daschinsky
Hi. But where is TC run? And I suppose, that https://travis-ci.com/github/apache/ignite/jobs/506675544 should be at least fixed пт, 21 мая 2021 г. в 10:22, Petr Ivanov : > > Hi, Ilya. > > > Left small comment on formatting issue. > Otherwise looks good! > > > Considering 3.8.1 maven support — we

Re: [DISCUSS] Python thin client development approach.

2021-05-18 Thread Ivan Daschinsky
talk about this few months ago but nothing changed. пт, 22 янв. 2021 г. в 16:12, Ivan Daschinsky : > > Igor, I've never talked about complete removal of TC builds. > I just suggested to add TC jobs for different python versions and use travis > heavily. > > Currently, we have done

Re: Extensions section on the downloads page

2021-05-17 Thread Ivan Daschinsky
ts that you can find on the downloads > > page > > > are added by INFRA). But the client-side JS works and can be tested > > locally. > > > > > > > > > - > > > Denis > > > > > > > > > On Fri, May 14,

Re: Proposal to remove explicit "GC disable" startup suggestion

2021-05-16 Thread Ivan Daschinsky
Hi, Val! Please take a look to java.nio.Bits.reserveMemory (jdk8). In this method you can see explicit call of System.gc() вс, 16 мая 2021 г., 01:22 Valentin Kulichenko : > Hi Ilya, > > Out of curiosity - what are the potential problems with memory buffers that > you're referring to? > > -Val >

Re: Extensions section on the downloads page

2021-05-14 Thread Ivan Daschinsky
>> What exactly are you trying to do? Denis, what I wanted I have described here -- https://issues.apache.org/jira/browse/IGNITE-14628 пт, 14 мая 2021 г. в 19:37, Ivan Daschinsky : > > Denis, there are screenshots from locally hosted site. > > https://imgbox.com/Zeqb0DVD &g

Re: Extensions section on the downloads page

2021-05-14 Thread Ivan Daschinsky
t; The thing is that Apache INFRA doesn't allow executing the server-side > logic anyway (the CGI code snippets that you can find on the downloads page > are added by INFRA). But the client-side JS works and can be tested locally. > > > - > Denis > > > On Fri, May 14, 20

Re: Extensions section on the downloads page

2021-05-14 Thread Ivan Daschinsky
hen merge > to the prod where scripts can be checked. > > > On Friday, May 14, 2021, Ivan Daschinsky wrote: > > > Denis, have you tried this? I tried, and see broken links and js code > > doesn't work. > > > > пт, 14 мая 2021 г. в 15:08, Denis Magda : > &g

Re: Extensions section on the downloads page

2021-05-14 Thread Ivan Daschinsky
o "download.html" locally. > > - > Denis > > > On Fri, May 14, 2021 at 2:40 AM Ivan Daschinsky > wrote: > > > Hi! And what about creating "download" page for thin clients? I > > created issue for this > > https://issues.apache.org/jira/bro

Re: Thin Clients: enable partition awareness by default

2021-05-14 Thread Ivan Daschinsky
ere were no major issues with this feature and it gives > > > good performance boost for many cases. > > > > > > Best Regards, > > > Igor > > > > > > > > > On Wed, May 12, 2021 at 5:18 PM Ivan Daschinsky > > wrote:

Re: Extensions section on the downloads page

2021-05-14 Thread Ivan Daschinsky
Hi! And what about creating "download" page for thin clients? I created issue for this https://issues.apache.org/jira/browse/IGNITE-14628 Btw, to be honest, I was unable to set up website with working download page locally. May be instruction is incomplete, but locally everything works fine

Re: Thin Clients: enable partition awareness by default

2021-05-12 Thread Ivan Daschinsky
Huge +1 from me. PA should be enabled by default. ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn : > > Igniters, > > Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1]. > > However, this feature is disabled by default in most clients for > compatibility reasons: > initially we

Re: [DISCUSSION] Array to BinaryObject serialization

2021-05-01 Thread Ivan Daschinsky
Hi! First of all, when array is serialized, marshaller actually DO PRESERVE type of element (seel org.apache.ignite.internal.binary.BinaryUtils#doReadObjectArray and org.apache.ignite.internal.binary.BinaryWriterExImpl#doWriteObjectArray). AFAIK, the motivation of Nickolay proposal, is the fact,

Re: [DISCUSSION] Documentation of thin clients (python, php, nodejs)

2021-04-23 Thread Ivan Daschinsky
t; And migrating the key information to readthedocs.io is really an option. > > Let's see what other Igniters think about this idea. > > I'd be glad if Igor Gusev could share his opinion on this. > > Regards, > Nikita > > > > чт, 22 апр. 2021 г. в 22:15, Ivan Daschi

[DISCUSSION] Documentation of thin clients (python, php, nodejs)

2021-04-22 Thread Ivan Daschinsky
release cycle, it is by default outdated and doesn't resemble the latest version of thin client. I suggest just remove all documentation from the main docs except simple installation instruction (i.e. pip install pyignite) and link to readthedocs.io Regards, Ivan Daschinsky

[ANNOUNCE] Apache IGNITE python thin client (pyignite) 0.4.0 released

2021-04-22 Thread Ivan Daschinsky
https://archive.apache.org/dist/ignite/pyignite/0.4.0/ Please let us know if you have any problems https://ignite.apache.org/community/resources.html#ask Regards, Ivan Daschinsky on behalf of the Apache Ignite community.

[RESULT][VOTE] Release pyignite-0.4.0-rc1

2021-04-21 Thread Ivan Daschinsky
Hello, Igniters! Release pyignite-0.4.0-rc1 has been accepted. The votes received: 3 "+1" binding votes 2 "+1" votes There are no "+0" or "-1" Here the votes received: - Denis Magda (binding) - Igor Sapego (binding) - Anton Vinogradov (binding) -

[jira] [Created] (IGNITE-14595) ExpiryPolicy support to python thin client

2021-04-20 Thread Ivan Daschinsky (Jira)
Ivan Daschinsky created IGNITE-14595: Summary: ExpiryPolicy support to python thin client Key: IGNITE-14595 URL: https://issues.apache.org/jira/browse/IGNITE-14595 Project: Ignite Issue

Re: [VOTE] Release pyignite 0.4.0-rc1

2021-04-17 Thread Ivan Daschinsky
; >> +1 >> >> Does it require documentation updates? >> >> - >> Denis >> >> >> On Fri, Apr 16, 2021 at 10:05 AM Ivan Daschinsky >> wrote: >> >> > Ivan Daschinsky >> > чт, 15 апр., 21:37 (19 часов назад) >> > ком

<    1   2   3   4   5   >