[jira] [Created] (IGNITE-11514) MVCC: Client listener: do not delegate implicit operation execution to separate thread for JDBC/ODBC

2019-03-11 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-11514: Summary: MVCC: Client listener: do not delegate implicit operation execution to separate thread for JDBC/ODBC Key: IGNITE-11514 URL: https://issues.apache.org/jira/browse/

[jira] [Created] (IGNITE-11515) MVCC: Make sure that multiple cursors are handled properly for JDBC/ODBC

2019-03-11 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-11515: Summary: MVCC: Make sure that multiple cursors are handled properly for JDBC/ODBC Key: IGNITE-11515 URL: https://issues.apache.org/jira/browse/IGNITE-11515 Pr

[jira] [Created] (IGNITE-11516) MVCC management and monitoring

2019-03-11 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-11516: Summary: MVCC management and monitoring Key: IGNITE-11516 URL: https://issues.apache.org/jira/browse/IGNITE-11516 Project: Ignite Issue Type: Task

Re: Ignite 2.8 Release: Time & Scope & Release manager

2019-03-11 Thread Anton Vinogradov
+1 to 2.7.1 release and such releases at future. On Sat, Mar 9, 2019 at 2:14 PM Vyacheslav Daradur wrote: > Denis, > > >> After this release, let's introduce a practice of maintenance > >> releases > > What a reason of waiting for 2.8 to introduce maintenance release? > > Let's prepare 2.7.1 wit

Re: Ignite 2.8 Release: Time & Scope & Release manager

2019-03-11 Thread Ilya Kasnacheev
Hello! > - *was hard to start the code samples (same issue as with cmd).* > - *The step above have to be repeated for every single sample* For this issue, do we have any solution at all? I'm afraid you will still have to add JVM args manually for every main class or test that you run.

[jira] [Created] (IGNITE-11517) MVCC: Support one-phase commit

2019-03-11 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-11517: Summary: MVCC: Support one-phase commit Key: IGNITE-11517 URL: https://issues.apache.org/jira/browse/IGNITE-11517 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-11518) SQL: Security checks are skipped on some SELECT paths

2019-03-11 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-11518: Summary: SQL: Security checks are skipped on some SELECT paths Key: IGNITE-11518 URL: https://issues.apache.org/jira/browse/IGNITE-11518 Project: Ignite

[jira] [Created] (IGNITE-11519) Web Console: Pack configuration tests in test-jar

2019-03-11 Thread Andrey Novikov (JIRA)
Andrey Novikov created IGNITE-11519: --- Summary: Web Console: Pack configuration tests in test-jar Key: IGNITE-11519 URL: https://issues.apache.org/jira/browse/IGNITE-11519 Project: Ignite Is

Re: Best Effort Affinity for thin clients

2019-03-11 Thread Igor Sapego
Pavel, That's right. Do you have other suggestions or objections? Best Regards, Igor On Fri, Mar 8, 2019 at 11:37 AM Pavel Tupitsyn wrote: > > maxConnectionNumber parameter > What's the idea? Follow the Best Effor Affinity logic, but establish up to > N connections? > > On Thu, Mar 7, 2019 a

[jira] [Created] (IGNITE-11520) SQL schema is overwritten by static query entity configuration

2019-03-11 Thread Denis Mekhanikov (JIRA)
Denis Mekhanikov created IGNITE-11520: - Summary: SQL schema is overwritten by static query entity configuration Key: IGNITE-11520 URL: https://issues.apache.org/jira/browse/IGNITE-11520 Project: I

[jira] [Created] (IGNITE-11521) Register listeners before joining the cluster

2019-03-11 Thread Lukas Polacek (JIRA)
Lukas Polacek created IGNITE-11521: -- Summary: Register listeners before joining the cluster Key: IGNITE-11521 URL: https://issues.apache.org/jira/browse/IGNITE-11521 Project: Ignite Issue Ty

Re: Ignite 2.8 Release: Time & Scope & Release manager

2019-03-11 Thread Dmitriy Pavlov
Hi Ignite Developers, I remember I've fixed one case of Corrupted Tree Exception, and this fix still not released. This is DB corruption, and loss of data: if user face with it he/she will probably ban Ignite for him/her preferences forever. If we select 2.7.1 (BTW it is more natural naming of p

Re: [MTCGA]: new failures in builds [3250936, 3250899] needs to be handled

2019-03-11 Thread Dmitriy Pavlov
It was infra issue, now these and similar tests are passing. чт, 7 мар. 2019 г. в 12:35, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that you were > a volunteer

Re: Disk page compression for Ignite persistent store

2019-03-11 Thread Alex Plehanov
Hello Igniters! I've implemented compression of WAL page snapshot records. Ticket [1], PR [2]. I've used page compression module implemented by Sergi Vladykin for page store. To configure WAL page records compression there are 2 properties added to DataStorageConfiguration: walPageCompression and

[MTCGA]: new failures in builds [3281871, 3281420, 3281282] needs to be handled

2019-03-11 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

[MTCGA]: new failures in builds [3222465, 3217217] needs to be handled

2019-03-11 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

Teamcity Bot DB corrupted (again)

2019-03-11 Thread Dmitriy Pavlov
Hi Ignite developers, Unfortunately, AI TC Bot DB is now lost. This means there can be a number of duplicate notifications on issues. I apologize for the inconvenience. I expect after during one day TC Bot DB will be re-loaded from the TC. Sincerely, Dmitriy Pavlov P.S. anticipating questions T

[jira] [Created] (IGNITE-11522) Ignite index in not working in a specific case

2019-03-11 Thread Mausam (JIRA)
Mausam created IGNITE-11522: --- Summary: Ignite index in not working in a specific case Key: IGNITE-11522 URL: https://issues.apache.org/jira/browse/IGNITE-11522 Project: Ignite Issue Type: Bug

[MTCGA]: new failures in builds [3168896, 3167648] needs to be handled

2019-03-11 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

[MTCGA]: new failures in builds [3269313, 3159881, 3157916, 3157778] needs to be handled

2019-03-11 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

Re: Best Effort Affinity for thin clients

2019-03-11 Thread Pavel Tupitsyn
My suggestion is a boolean flag in client configuration: DisableAffinityAwareness And use old random/round-robin behavior with only one active connection. On Mon, Mar 11, 2019 at 1:36 PM Igor Sapego wrote: > Pavel, > > That's right. Do you have other suggestions or objections? > > Best Regards,

[jira] [Created] (IGNITE-11523) Can't cast null value from Cassandra table primitive column to primitive value used in domain object model

2019-03-11 Thread Xinmin Wang (JIRA)
Xinmin Wang created IGNITE-11523: Summary: Can't cast null value from Cassandra table primitive column to primitive value used in domain object model Key: IGNITE-11523 URL: https://issues.apache.org/jira/browse/IG

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

2019-03-11 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize