Re: Thin client: transactions support

2019-05-20 Thread Alex Plehanov
Igor, Perhaps we don't really need to use server's default values for tx parameters. It's a minor fix and can be easily implemented if it will be required in the future. I will update IEP tomorrow regarding point 1 and point 3. Thanks for your feedback. пн, 20 мая 2019 г. в 15:24, Igor Sapego :

Re: [Discussion] Documentation process improvement: Release notes

2019-05-20 Thread Garrett Alley
I like the flag, it would help cut down on the work involved in creating the release notes. Eventually, we may want to group the fixes "by component" in the release notes. -g- On Mon, May 20, 2019 at 4:28 AM Ilya Kasnacheev wrote: > Hello! > > I think it definitely makes sense to have Release

Re: Thin client: transactions support

2019-05-20 Thread Igor Sapego
Ivan, This may be a good point for a DBMS, but Ignite is much more than just a DBMS and Ignite client code is not just an SQL query (which execution inherently heavily depends on DBMS). With database user is expecting that server have a lot of control on query execution. But with Ignite, in my

Re: [Discussion] Documentation process improvement: Release notes

2019-05-20 Thread Ilya Kasnacheev
Hello! I think it definitely makes sense to have Release Notes field in JIRA tickets (start using it if it is already present?). Not sure about the flag. Regards, -- Ilya Kasnacheev пн, 20 мая 2019 г. в 13:23, Dmitriy Pavlov : > Hi Ignite Developers, > > Kindly Reminder, please review the

Re: Thin client: transactions support

2019-05-20 Thread Павлухин Иван
Igor, Alex, Regarding point 1. I must say that SQL vendors usually allow to configure default timeouts and a transaction isolation on a server side. E.g. in MySQL you can do a following: set local tx_isolation = -- per SQL client session (usually physical network connection) set global

Re: Thin client: transactions support

2019-05-20 Thread Igor Sapego
1. In my opinion, having client-specific transaction parameters is expected for client when have different arguments depending on server seems unexpected and can lead to hard-to-debug bugs and issues when updating from old to new server versions. Also it goes against common practice with arguments

Re: [Discussion] Documentation process improvement: Release notes

2019-05-20 Thread Dmitriy Pavlov
Hi Ignite Developers, Kindly Reminder, please review the proposed changes and share your vision. I would appreciate if this change will be approved by community members, but not via silence. Sincerely Dmitriy Pavlov вт, 14 мая 2019 г. в 15:19, Dmitriy Pavlov : > Hi Igniters, > > During the

Re: Thin client: transactions support

2019-05-20 Thread Alex Plehanov
Hi, Igor 1. I think it's better to have the ability to configure transaction parameters (for example configure default timeout for all clients) on server-side, then don't have such ability and always use some predefined client-side values (which can be different for different client

Re: [ML] Machine Learning Pipeline Improvement

2019-05-20 Thread Alexey Zinoviev
Dear Manu it could be a great idea! Could you please provide any examples of Apache Arrow integration for speed up ML computation in another ML frameworks, it would be very helpful! Sincerely yours Alexey Zinovyev -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: [DISCUSSION] Channel communication between nodes

2019-05-20 Thread Alexey Goncharuk
Maxim, I left response in the ticket. пт, 17 мая 2019 г. в 12:04, Maxim Muzafarov : > Igniters, > > > I've implemented the file transfer machinery between grid nodes over > Communication SPI covered by JIRA [1] and as the first part of IEP-28 > [3]. Please, consider my PR [2] to be reviewed and