[jira] [Created] (IGNITE-6876) ODBC: Add support for SQL_ATTR_CONNECTION_TIMEOUT

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-6876:


 Summary: ODBC: Add support for SQL_ATTR_CONNECTION_TIMEOUT
 Key: IGNITE-6876
 URL: https://issues.apache.org/jira/browse/IGNITE-6876
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: odbc
Affects Versions: 2.1
Reporter: Alexey Popov


Remote ODBC client should be able to request a timeout for socket send/receive 
operations. It should be done with SQL_ATTR_CONNECTION_TIMEOUT attribute.
If an application with ODBC driver experiences a timeout for some query, it can 
continue to work after closing the connection and establishing a new one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6865) Wrong map query build when using group by in both the outer and inner queries

[Alin Andrei Corodescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alin Andrei Corodescu updated IGNITE-6865:
--
Summary: Wrong map query build when using group by in both the outer and 
inner queries  (was: Wrong map query build using)

> Wrong map query build when using group by in both the outer and inner queries
> -
>
> Key: IGNITE-6865
> URL: https://issues.apache.org/jira/browse/IGNITE-6865
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Affects Versions: 2.3
>Reporter: Alin Andrei Corodescu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-5932) Integrate communication with coordinator in tx protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-5932.
---

> Integrate communication with coordinator in tx protocol
> ---
>
> Key: IGNITE-5932
> URL: https://issues.apache.org/jira/browse/IGNITE-5932
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need integrate communication with coordinator in transactions protocol:
> - reading transaction need request read ID from coordinator
> - after locks are acquired need request ID from coordinator
> - this ID should be passed to primary/backups and passed to update
> - after tx is committed need notify coordinator (note: need make sure that 
> this notification is processed in such way so that thread executed 
> transaction will see all his changes)
> Notes:
> - there are differences in prepare logic for 
> optimistic/pessimistic/serializable transactions, so most probably work with 
> coordinator should be implemented separately for these tx types
> - need support case when coordinator fails during prepare (need think is 
> necessary rollback and retry tx or switch to next assigned coordinator)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-3484) MVCC data structure for getAll operation

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-3484.
---

> MVCC data structure for getAll operation
> 
>
> Key: IGNITE-3484
> URL: https://issues.apache.org/jira/browse/IGNITE-3484
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need implement some data structure to store/get multiple entry versions:
> - committed value at first is stored in separate data structure (there also 
> need store related tx id to filter out data for non-finished transactions), 
> probably existing BPlusTree can be used
> - periodically need flush data for finished transaction in 'main' hash index
> - 'getAll' operation should include max 'visible' ID and list of active 
> transactions, this information should be used to find last 'visible' version 
> in 'mvcc' or 'main' index



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-5937) Mvcc data structure for SQL queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-5937.
---

> Mvcc data structure for SQL queries
> ---
>
> Key: IGNITE-5937
> URL: https://issues.apache.org/jira/browse/IGNITE-5937
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need implement some data structure to store/query multiple entry versions.
> One possible option:
> - committed value at first is stored in separate BPlusTree index (there also 
> need store related tx id to filter out data for non-finished transactions)
> - periodically flush data for finished transaction in 'main' index
> - for SQL queries need merge result from main index and filtered 'mvcc' 
> index. Note: it is possible 'mvcc' index will contain multiple committed 
> versions of the same entry, need make sure only one last one will appear in 
> result.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6149) Create mvcc prototype application

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-6149.
---

> Create mvcc prototype application
> -
>
> Key: IGNITE-6149
> URL: https://issues.apache.org/jira/browse/IGNITE-6149
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
> Attachments: MvccTestApp.java
>
>
> Need create simple prototype application to verify major concepts:
> - which data should be stored on coordinator and on data nodes
> - filtering algorithm for getAll and sql operations
> - clean up of committed versions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5933) Integrate mvcc support in cache.getAll protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-5933:
---

Assignee: Semen Boikov

> Integrate mvcc support in cache.getAll protocol
> ---
>
> Key: IGNITE-5933
> URL: https://issues.apache.org/jira/browse/IGNITE-5933
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need integrate mvcc support in cache.getAll protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in get requests and in local 'get'
> - notify coordinator after getAll completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6149) Create mvcc prototype application

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-6149:
---

Assignee: Semen Boikov

> Create mvcc prototype application
> -
>
> Key: IGNITE-6149
> URL: https://issues.apache.org/jira/browse/IGNITE-6149
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
> Attachments: MvccTestApp.java
>
>
> Need create simple prototype application to verify major concepts:
> - which data should be stored on coordinator and on data nodes
> - filtering algorithm for getAll and sql operations
> - clean up of committed versions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-3479) Coordinator(s) for global transaction ordering

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-3479.
---

> Coordinator(s) for global transaction ordering
> --
>
> Key: IGNITE-3479
> URL: https://issues.apache.org/jira/browse/IGNITE-3479
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Current transaction ID will not work for SQL MVCC ordering because two 
> transaction IDs are not in total order across the cluster.
> One of the approaches is to have a dedicated coordinator which will assign a 
> continuously growing transaction ID for each committed transaction. This ID 
> must be acquired by each transaction at the last step of PREPARE stage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5937) Mvcc data structure for SQL queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-5937:
---

Assignee: Semen Boikov

> Mvcc data structure for SQL queries
> ---
>
> Key: IGNITE-5937
> URL: https://issues.apache.org/jira/browse/IGNITE-5937
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need implement some data structure to store/query multiple entry versions.
> One possible option:
> - committed value at first is stored in separate BPlusTree index (there also 
> need store related tx id to filter out data for non-finished transactions)
> - periodically flush data for finished transaction in 'main' index
> - for SQL queries need merge result from main index and filtered 'mvcc' 
> index. Note: it is possible 'mvcc' index will contain multiple committed 
> versions of the same entry, need make sure only one last one will appear in 
> result.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6709) Support mvcc filter for H2TreeIndex.findFirstOrLast

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-6709.
---

> Support mvcc filter for H2TreeIndex.findFirstOrLast
> ---
>
> Key: IGNITE-6709
> URL: https://issues.apache.org/jira/browse/IGNITE-6709
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Need implement possibility to pass filter in findFirst/findLast (test already 
> exists CacheMvccSqlQueriesTest.testMaxMinTransactional).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-5933) Integrate mvcc support in cache.getAll protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-5933.
---

> Integrate mvcc support in cache.getAll protocol
> ---
>
> Key: IGNITE-5933
> URL: https://issues.apache.org/jira/browse/IGNITE-5933
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need integrate mvcc support in cache.getAll protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in get requests and in local 'get'
> - notify coordinator after getAll completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5934) Integrate mvcc support in sql query protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5934:

Component/s: (was: cache)

> Integrate mvcc support in sql query protocol
> 
>
> Key: IGNITE-5934
> URL: https://issues.apache.org/jira/browse/IGNITE-5934
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Need integrate mvcc support in sql query protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in sql requests and in sql queries
> - notify coordinator after query completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6149) Create mvcc prototype application

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6149:

Fix Version/s: (was: 2.3)
   2.4

> Create mvcc prototype application
> -
>
> Key: IGNITE-6149
> URL: https://issues.apache.org/jira/browse/IGNITE-6149
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 2.4
>
> Attachments: MvccTestApp.java
>
>
> Need create simple prototype application to verify major concepts:
> - which data should be stored on coordinator and on data nodes
> - filtering algorithm for getAll and sql operations
> - clean up of committed versions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6709) Support mvcc filter for H2TreeIndex.findFirstOrLast

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6709:

Component/s: (was: cache)
 sql

> Support mvcc filter for H2TreeIndex.findFirstOrLast
> ---
>
> Key: IGNITE-6709
> URL: https://issues.apache.org/jira/browse/IGNITE-6709
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Need implement possibility to pass filter in findFirst/findLast (test already 
> exists CacheMvccSqlQueriesTest.testMaxMinTransactional).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6739) Add tests verifying queries functionality is not broken if mvcc is enabled

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6739:

Component/s: sql

> Add tests verifying queries functionality is not broken if mvcc is enabled
> --
>
> Key: IGNITE-6739
> URL: https://issues.apache.org/jira/browse/IGNITE-6739
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Add tests verifying queries functionality is not broken if mvcc is enabled:
> - full text indexes
> - queries with indexing spi
> - CacheConfiguration with setQueryParallelism
> - lazy queries (SqlFieldsQuery.setLazy(true))
> - collocated queries (SqlFieldsQuery.setCollocated)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6739) Add tests verifying queries functionality is not broken if mvcc is enabled

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6739:

Component/s: (was: cache)

> Add tests verifying queries functionality is not broken if mvcc is enabled
> --
>
> Key: IGNITE-6739
> URL: https://issues.apache.org/jira/browse/IGNITE-6739
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Add tests verifying queries functionality is not broken if mvcc is enabled:
> - full text indexes
> - queries with indexing spi
> - CacheConfiguration with setQueryParallelism
> - lazy queries (SqlFieldsQuery.setLazy(true))
> - collocated queries (SqlFieldsQuery.setCollocated)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-3479) Coordinator(s) for global transaction ordering

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3479:

Fix Version/s: 2.4

> Coordinator(s) for global transaction ordering
> --
>
> Key: IGNITE-3479
> URL: https://issues.apache.org/jira/browse/IGNITE-3479
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Current transaction ID will not work for SQL MVCC ordering because two 
> transaction IDs are not in total order across the cluster.
> One of the approaches is to have a dedicated coordinator which will assign a 
> continuously growing transaction ID for each committed transaction. This ID 
> must be acquired by each transaction at the last step of PREPARE stage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5937) Mvcc data structure for SQL queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5937:

Component/s: sql

> Mvcc data structure for SQL queries
> ---
>
> Key: IGNITE-5937
> URL: https://issues.apache.org/jira/browse/IGNITE-5937
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Need implement some data structure to store/query multiple entry versions.
> One possible option:
> - committed value at first is stored in separate BPlusTree index (there also 
> need store related tx id to filter out data for non-finished transactions)
> - periodically flush data for finished transaction in 'main' index
> - for SQL queries need merge result from main index and filtered 'mvcc' 
> index. Note: it is possible 'mvcc' index will contain multiple committed 
> versions of the same entry, need make sure only one last one will appear in 
> result.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6738) Support mvcc filter for local sql queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6738:

Component/s: (was: cache)

> Support mvcc filter for local sql queries
> -
>
> Key: IGNITE-6738
> URL: https://issues.apache.org/jira/browse/IGNITE-6738
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Need receive/release mvcc version for queries with setLocal flag set, there 
> are already some tests in CacheMvccSqlQueriesTest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5932) Integrate communication with coordinator in tx protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5932:

Fix Version/s: 2.4

> Integrate communication with coordinator in tx protocol
> ---
>
> Key: IGNITE-5932
> URL: https://issues.apache.org/jira/browse/IGNITE-5932
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Need integrate communication with coordinator in transactions protocol:
> - reading transaction need request read ID from coordinator
> - after locks are acquired need request ID from coordinator
> - this ID should be passed to primary/backups and passed to update
> - after tx is committed need notify coordinator (note: need make sure that 
> this notification is processed in such way so that thread executed 
> transaction will see all his changes)
> Notes:
> - there are differences in prepare logic for 
> optimistic/pessimistic/serializable transactions, so most probably work with 
> coordinator should be implemented separately for these tx types
> - need support case when coordinator fails during prepare (need think is 
> necessary rollback and retry tx or switch to next assigned coordinator)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5937) Mvcc data structure for SQL queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5937:

Component/s: (was: cache)

> Mvcc data structure for SQL queries
> ---
>
> Key: IGNITE-5937
> URL: https://issues.apache.org/jira/browse/IGNITE-5937
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Need implement some data structure to store/query multiple entry versions.
> One possible option:
> - committed value at first is stored in separate BPlusTree index (there also 
> need store related tx id to filter out data for non-finished transactions)
> - periodically flush data for finished transaction in 'main' index
> - for SQL queries need merge result from main index and filtered 'mvcc' 
> index. Note: it is possible 'mvcc' index will contain multiple committed 
> versions of the same entry, need make sure only one last one will appear in 
> result.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6709) Support mvcc filter for H2TreeIndex.findFirstOrLast

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6709:

Fix Version/s: 2.4

> Support mvcc filter for H2TreeIndex.findFirstOrLast
> ---
>
> Key: IGNITE-6709
> URL: https://issues.apache.org/jira/browse/IGNITE-6709
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Need implement possibility to pass filter in findFirst/findLast (test already 
> exists CacheMvccSqlQueriesTest.testMaxMinTransactional).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5936) Cleanup of not needed and committed versions

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5936:

Fix Version/s: 2.4

> Cleanup of not needed and committed versions
> 
>
> Key: IGNITE-5936
> URL: https://issues.apache.org/jira/browse/IGNITE-5936
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> At first committed data is stored in separate data structure.Need implement 
> some procedure to remove from mvcc storage versions which are not needed 
> anymore and flush committed versions in main storage. Version which is safe 
> to remove (there are not readers using this version) should be somehow passed 
> from coordinator to servers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6738) Support mvcc filter for local sql queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6738:

Fix Version/s: 2.4

> Support mvcc filter for local sql queries
> -
>
> Key: IGNITE-6738
> URL: https://issues.apache.org/jira/browse/IGNITE-6738
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Need receive/release mvcc version for queries with setLocal flag set, there 
> are already some tests in CacheMvccSqlQueriesTest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6738) Support mvcc filter for local sql queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6738:

Component/s: sql

> Support mvcc filter for local sql queries
> -
>
> Key: IGNITE-6738
> URL: https://issues.apache.org/jira/browse/IGNITE-6738
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Need receive/release mvcc version for queries with setLocal flag set, there 
> are already some tests in CacheMvccSqlQueriesTest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6739) Add tests verifying queries functionality is not broken if mvcc is enabled

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6739:

Fix Version/s: 2.4

> Add tests verifying queries functionality is not broken if mvcc is enabled
> --
>
> Key: IGNITE-6739
> URL: https://issues.apache.org/jira/browse/IGNITE-6739
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Add tests verifying queries functionality is not broken if mvcc is enabled:
> - full text indexes
> - queries with indexing spi
> - CacheConfiguration with setQueryParallelism
> - lazy queries (SqlFieldsQuery.setLazy(true))
> - collocated queries (SqlFieldsQuery.setCollocated)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6874) MVCC: base functionality

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6874:

Component/s: (was: sql)

> MVCC: base functionality
> 
>
> Key: IGNITE-6874
> URL: https://issues.apache.org/jira/browse/IGNITE-6874
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: cache
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> This is an umbrella ticket for base MVCC functionality:
> 1) Version management
> 2) Cache transactions support
> 3) SQL SELECTs support



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5934) Integrate mvcc support in sql query protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5934:

Fix Version/s: 2.4

> Integrate mvcc support in sql query protocol
> 
>
> Key: IGNITE-5934
> URL: https://issues.apache.org/jira/browse/IGNITE-5934
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Semen Boikov
> Fix For: 2.4
>
>
> Need integrate mvcc support in sql query protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in sql requests and in sql queries
> - notify coordinator after query completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6353) Integrate mvcc support in scan query protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6353:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Integrate mvcc support in scan query protocol
> -
>
> Key: IGNITE-6353
> URL: https://issues.apache.org/jira/browse/IGNITE-6353
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Need integrate mvcc support in scan query protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in query requests and in cache iterators
> - notify coordinator after query completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6459) Implement metrics to monitor mvcc coordinator performance

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6459:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Implement metrics to monitor mvcc coordinator performance
> -
>
> Key: IGNITE-6459
> URL: https://issues.apache.org/jira/browse/IGNITE-6459
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Need provide some public metrics which allow to to monitor mvcc coordinator 
> performance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6754) Support coordinator change while sql is in progress

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6754:

Component/s: sql

> Support coordinator change while sql is in progress
> ---
>
> Key: IGNITE-6754
> URL: https://issues.apache.org/jira/browse/IGNITE-6754
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Semen Boikov
>
> Need support coordinator change while sql queries are in progress (see how 
> MvccQueryTracker is used for cache.getAll operation). Need make sure this is 
> handled for both local/non-local queries and add tests similar to 
> CacheMvccTransactionsTest.testCleanupWaitsForGet. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6458) Implement possibility to manually change mvcc coordinator

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6458:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Implement possibility to manually change mvcc coordinator
> -
>
> Key: IGNITE-6458
> URL: https://issues.apache.org/jira/browse/IGNITE-6458
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Need provide some ability to manually switch mvcc coordinator, probably via 
> MBean.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5935) Integrate mvcc support in tx recovery protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5935:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Integrate mvcc support in tx recovery protocol
> --
>
> Key: IGNITE-5935
> URL: https://issues.apache.org/jira/browse/IGNITE-5935
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>
> Need make sure tx recovery work properly with mvcc enabled:
> - tx IDs are generated and not lost if transaction is committed by recovery 
> procedure
> - tx should be removed from list of active transactions on coordinator



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6754) Support coordinator change while sql is in progress

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6754:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Support coordinator change while sql is in progress
> ---
>
> Key: IGNITE-6754
> URL: https://issues.apache.org/jira/browse/IGNITE-6754
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Semen Boikov
>
> Need support coordinator change while sql queries are in progress (see how 
> MvccQueryTracker is used for cache.getAll operation). Need make sure this is 
> handled for both local/non-local queries and add tests similar to 
> CacheMvccTransactionsTest.testCleanupWaitsForGet. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6875) MVCC: advanced features

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6875:
---

 Summary: MVCC: advanced features
 Key: IGNITE-6875
 URL: https://issues.apache.org/jira/browse/IGNITE-6875
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: cache
Reporter: Vladimir Ozerov


This is umbrella ticket for advanced MVCC features, focusing on failover, 
performance, scan queries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5936) Cleanup of not needed and committed versions

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5936:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Cleanup of not needed and committed versions
> 
>
> Key: IGNITE-5936
> URL: https://issues.apache.org/jira/browse/IGNITE-5936
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> At first committed data is stored in separate data structure.Need implement 
> some procedure to remove from mvcc storage versions which are not needed 
> anymore and flush committed versions in main storage. Version which is safe 
> to remove (there are not readers using this version) should be somehow passed 
> from coordinator to servers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5934) Integrate mvcc support in sql query protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5934:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Integrate mvcc support in sql query protocol
> 
>
> Key: IGNITE-5934
> URL: https://issues.apache.org/jira/browse/IGNITE-5934
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Need integrate mvcc support in sql query protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in sql requests and in sql queries
> - notify coordinator after query completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6863) visorcmd: 'cache -a' shows nodes that are not matched by nodeFilter

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-6863:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Looks good.

Please add test with node filter and assign to [~pkonstantinov] for test.

> visorcmd: 'cache -a' shows nodes that are not matched by nodeFilter
> ---
>
> Key: IGNITE-6863
> URL: https://issues.apache.org/jira/browse/IGNITE-6863
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: visor
>Affects Versions: 2.3
>Reporter: Denis Mekhanikov
>Assignee: Vasiliy Sisko
> Attachments: node-filter.zip
>
>
> 'cache -a' command shows all nodes in the detailed summary, even those, which 
> are not matched by a configured node filter.
> Please find attached archive with the reproducing example project.
> LOCAL cache also has this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-3479) Coordinator(s) for global transaction ordering

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3479:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Coordinator(s) for global transaction ordering
> --
>
> Key: IGNITE-3479
> URL: https://issues.apache.org/jira/browse/IGNITE-3479
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
>
> Current transaction ID will not work for SQL MVCC ordering because two 
> transaction IDs are not in total order across the cluster.
> One of the approaches is to have a dedicated coordinator which will assign a 
> continuously growing transaction ID for each committed transaction. This ID 
> must be acquired by each transaction at the last step of PREPARE stage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5932) Integrate communication with coordinator in tx protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5932:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Integrate communication with coordinator in tx protocol
> ---
>
> Key: IGNITE-5932
> URL: https://issues.apache.org/jira/browse/IGNITE-5932
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>
> Need integrate communication with coordinator in transactions protocol:
> - reading transaction need request read ID from coordinator
> - after locks are acquired need request ID from coordinator
> - this ID should be passed to primary/backups and passed to update
> - after tx is committed need notify coordinator (note: need make sure that 
> this notification is processed in such way so that thread executed 
> transaction will see all his changes)
> Notes:
> - there are differences in prepare logic for 
> optimistic/pessimistic/serializable transactions, so most probably work with 
> coordinator should be implemented separately for these tx types
> - need support case when coordinator fails during prepare (need think is 
> necessary rollback and retry tx or switch to next assigned coordinator)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5933) Integrate mvcc support in cache.getAll protocol

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5933:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Integrate mvcc support in cache.getAll protocol
> ---
>
> Key: IGNITE-5933
> URL: https://issues.apache.org/jira/browse/IGNITE-5933
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Need integrate mvcc support in cache.getAll protocol:
> - request current ID and list of active txs from coordinator
> - pass this info in get requests and in local 'get'
> - notify coordinator after getAll completed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-3484) MVCC data structure for getAll operation

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3484:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> MVCC data structure for getAll operation
> 
>
> Key: IGNITE-3484
> URL: https://issues.apache.org/jira/browse/IGNITE-3484
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
>
> Need implement some data structure to store/get multiple entry versions:
> - committed value at first is stored in separate data structure (there also 
> need store related tx id to filter out data for non-finished transactions), 
> probably existing BPlusTree can be used
> - periodically need flush data for finished transaction in 'main' hash index
> - 'getAll' operation should include max 'visible' ID and list of active 
> transactions, this information should be used to find last 'visible' version 
> in 'mvcc' or 'main' index



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5937) Mvcc data structure for SQL queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5937:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Mvcc data structure for SQL queries
> ---
>
> Key: IGNITE-5937
> URL: https://issues.apache.org/jira/browse/IGNITE-5937
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Need implement some data structure to store/query multiple entry versions.
> One possible option:
> - committed value at first is stored in separate BPlusTree index (there also 
> need store related tx id to filter out data for non-finished transactions)
> - periodically flush data for finished transaction in 'main' index
> - for SQL queries need merge result from main index and filtered 'mvcc' 
> index. Note: it is possible 'mvcc' index will contain multiple committed 
> versions of the same entry, need make sure only one last one will appear in 
> result.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-3478) Multi-version concurrency control

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-3478:
---

Assignee: (was: Vladimir Ozerov)

> Multi-version concurrency control
> -
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>  Labels: important
>
> Current Ignite SQL does not take into account transaction boundaries. For 
> example, if a transaction atomically changes balance of two accounts, then a 
> concurrent SQL query can see partially committed transaction. This works for 
> data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are 
> taken into account for SQL query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6149) Create mvcc prototype application

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6149:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Create mvcc prototype application
> -
>
> Key: IGNITE-6149
> URL: https://issues.apache.org/jira/browse/IGNITE-6149
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 2.3
>
> Attachments: MvccTestApp.java
>
>
> Need create simple prototype application to verify major concepts:
> - which data should be stored on coordinator and on data nodes
> - filtering algorithm for getAll and sql operations
> - clean up of committed versions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-3478) Multi-version concurrency control

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-3478:
---

Assignee: (was: Semen Boikov)

> Multi-version concurrency control
> -
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>  Labels: important
>
> Current Ignite SQL does not take into account transaction boundaries. For 
> example, if a transaction atomically changes balance of two accounts, then a 
> concurrent SQL query can see partially committed transaction. This works for 
> data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are 
> taken into account for SQL query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-3478) Multi-version concurrency control

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-3478:
---

Assignee: Vladimir Ozerov

> Multi-version concurrency control
> -
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Vladimir Ozerov
>  Labels: important
>
> Current Ignite SQL does not take into account transaction boundaries. For 
> example, if a transaction atomically changes balance of two accounts, then a 
> concurrent SQL query can see partially committed transaction. This works for 
> data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are 
> taken into account for SQL query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6739) Add tests verifying queries functionality is not broken if mvcc is enabled

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6739:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Add tests verifying queries functionality is not broken if mvcc is enabled
> --
>
> Key: IGNITE-6739
> URL: https://issues.apache.org/jira/browse/IGNITE-6739
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>
> Add tests verifying queries functionality is not broken if mvcc is enabled:
> - full text indexes
> - queries with indexing spi
> - CacheConfiguration with setQueryParallelism
> - lazy queries (SqlFieldsQuery.setLazy(true))
> - collocated queries (SqlFieldsQuery.setCollocated)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6738) Support mvcc filter for local sql queries

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6738:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Support mvcc filter for local sql queries
> -
>
> Key: IGNITE-6738
> URL: https://issues.apache.org/jira/browse/IGNITE-6738
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
>
> Need receive/release mvcc version for queries with setLocal flag set, there 
> are already some tests in CacheMvccSqlQueriesTest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6709) Support mvcc filter for H2TreeIndex.findFirstOrLast

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6709:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3478)

> Support mvcc filter for H2TreeIndex.findFirstOrLast
> ---
>
> Key: IGNITE-6709
> URL: https://issues.apache.org/jira/browse/IGNITE-6709
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
>
> Need implement possibility to pass filter in findFirst/findLast (test already 
> exists CacheMvccSqlQueriesTest.testMaxMinTransactional).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6874) MVCC: base functionality

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6874:
---

 Summary: MVCC: base functionality
 Key: IGNITE-6874
 URL: https://issues.apache.org/jira/browse/IGNITE-6874
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: cache, sql
Reporter: Vladimir Ozerov
 Fix For: 2.4


This is an umbrella ticket for base MVCC functionality:
1) Version management
2) Cache transactions support
3) SQL SELECTs support



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4192) SQL TX: JDBC driver support

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4192:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-4191)

> SQL TX: JDBC driver support
> ---
>
> Key: IGNITE-4192
> URL: https://issues.apache.org/jira/browse/IGNITE-4192
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>
> To support execution of DML and SELECT statements inside of a transaction 
> started from JDBC driver side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4193) SQL TX: ODBC driver support

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4193:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-4191)

> SQL TX: ODBC driver support
> ---
>
> Key: IGNITE-4193
> URL: https://issues.apache.org/jira/browse/IGNITE-4193
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Reporter: Denis Magda
>
> To support execution of DML and SELECT statements inside of a transaction 
> started from ODBC driver side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4194) DML: transactional support for DML statements

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4194:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-4191)

> DML: transactional support for DML statements
> -
>
> Key: IGNITE-4194
> URL: https://issues.apache.org/jira/browse/IGNITE-4194
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>
> To support execution of DML and statements inside of a transaction started 
> from DML API side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-4194) DML: transactional support for DML statements

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-4194.
---

> DML: transactional support for DML statements
> -
>
> Key: IGNITE-4194
> URL: https://issues.apache.org/jira/browse/IGNITE-4194
> Project: Ignite
>  Issue Type: Sub-task
>  Components: sql
>Reporter: Denis Magda
>
> To support execution of DML and statements inside of a transaction started 
> from DML API side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-4194) DML: transactional support for DML statements

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-4194.
-
Resolution: Won't Fix

This will be done as a part of multiple tickets.linked to parent umbrella.

> DML: transactional support for DML statements
> -
>
> Key: IGNITE-4194
> URL: https://issues.apache.org/jira/browse/IGNITE-4194
> Project: Ignite
>  Issue Type: Sub-task
>  Components: sql
>Reporter: Denis Magda
>
> To support execution of DML and statements inside of a transaction started 
> from DML API side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4193) SQL TX: ODBC driver support

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4193:

Summary: SQL TX: ODBC driver support  (was: ODBC: transactional support for 
DML and SELECT statements)

> SQL TX: ODBC driver support
> ---
>
> Key: IGNITE-4193
> URL: https://issues.apache.org/jira/browse/IGNITE-4193
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Reporter: Denis Magda
>
> To support execution of DML and SELECT statements inside of a transaction 
> started from ODBC driver side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4192) SQL TX: JDBC driver support

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4192:

Summary: SQL TX: JDBC driver support  (was: JDBC: transactional support for 
DML and SELECT statements)

> SQL TX: JDBC driver support
> ---
>
> Key: IGNITE-4192
> URL: https://issues.apache.org/jira/browse/IGNITE-4192
> Project: Ignite
>  Issue Type: Sub-task
>  Components: sql
>Reporter: Denis Magda
>
> To support execution of DML and SELECT statements inside of a transaction 
> started from JDBC driver side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4191) SQL: support transactions

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4191:

Labels: important  (was: )

> SQL: support transactions
> -
>
> Key: IGNITE-4191
> URL: https://issues.apache.org/jira/browse/IGNITE-4191
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>  Labels: iep-3, important
>
> Presently there is no any way to execute data modification statements and 
> SELECT queries in a transactional fashion using our JDBC/ODBC drivers and DML 
> API.
> This can be fully supported once MVCC is ready and released.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4191) SQL: support transactions

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4191:

Labels: iep-3 important  (was: important)

> SQL: support transactions
> -
>
> Key: IGNITE-4191
> URL: https://issues.apache.org/jira/browse/IGNITE-4191
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>  Labels: iep-3, important
>
> Presently there is no any way to execute data modification statements and 
> SELECT queries in a transactional fashion using our JDBC/ODBC drivers and DML 
> API.
> This can be fully supported once MVCC is ready and released.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4191) SQL: support transactions

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4191:

Summary: SQL: support transactions  (was: Transactional support at the 
level of Ignite drivers and DML)

> SQL: support transactions
> -
>
> Key: IGNITE-4191
> URL: https://issues.apache.org/jira/browse/IGNITE-4191
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>  Labels: iep-3, important
>
> Presently there is no any way to execute data modification statements and 
> SELECT queries in a transactional fashion using our JDBC/ODBC drivers and DML 
> API.
> This can be fully supported once MVCC is ready and released.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6076) SQL: Local query should not go through map-reduce phase

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-6076.
---

> SQL: Local query should not go through map-reduce phase
> ---
>
> Key: IGNITE-6076
> URL: https://issues.apache.org/jira/browse/IGNITE-6076
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: performance
>
> Typical query execution consists of map and reduce phases. But if {{local}} 
> flag is set, there is no need for splitting. Instead, we should execute the 
> request in a single map phase, without involving reducer at all. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6076) SQL: Local query should not go through map-reduce phase

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-6076.
-
Resolution: Won't Fix

I was wrong - local query execution is already optimized this way.

> SQL: Local query should not go through map-reduce phase
> ---
>
> Key: IGNITE-6076
> URL: https://issues.apache.org/jira/browse/IGNITE-6076
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: performance
>
> Typical query execution consists of map and reduce phases. But if {{local}} 
> flag is set, there is no need for splitting. Instead, we should execute the 
> request in a single map phase, without involving reducer at all. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-3478) Multi-version concurrency control

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3478:

Summary: Multi-version concurrency control  (was: Transactional SQL (mvcc))

> Multi-version concurrency control
> -
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
>  Labels: important
>
> Current Ignite SQL does not take into account transaction boundaries. For 
> example, if a transaction atomically changes balance of two accounts, then a 
> concurrent SQL query can see partially committed transaction. This works for 
> data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are 
> taken into account for SQL query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6863) visorcmd: 'cache -a' shows nodes that are not matched by nodeFilter

[Vasiliy Sisko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-6863:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> visorcmd: 'cache -a' shows nodes that are not matched by nodeFilter
> ---
>
> Key: IGNITE-6863
> URL: https://issues.apache.org/jira/browse/IGNITE-6863
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: visor
>Affects Versions: 2.3
>Reporter: Denis Mekhanikov
>Assignee: Alexey Kuznetsov
> Attachments: node-filter.zip
>
>
> 'cache -a' command shows all nodes in the detailed summary, even those, which 
> are not matched by a configured node filter.
> Please find attached archive with the reproducing example project.
> LOCAL cache also has this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6863) visorcmd: 'cache -a' shows nodes that are not matched by nodeFilter

[Vasiliy Sisko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249166#comment-16249166
 ] 

Vasiliy Sisko commented on IGNITE-6863:
---

Fixed showing of cache info when cache is not configured for node.
Fixed NPE for client node when data storage is not configured.

> visorcmd: 'cache -a' shows nodes that are not matched by nodeFilter
> ---
>
> Key: IGNITE-6863
> URL: https://issues.apache.org/jira/browse/IGNITE-6863
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: visor
>Affects Versions: 2.3
>Reporter: Denis Mekhanikov
>Assignee: Vasiliy Sisko
> Attachments: node-filter.zip
>
>
> 'cache -a' command shows all nodes in the detailed summary, even those, which 
> are not matched by a configured node filter.
> Please find attached archive with the reproducing example project.
> LOCAL cache also has this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6873) Web console: some error messages are too technical

[Ilya Borisov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Borisov reassigned IGNITE-6873:


Assignee: Andrey Novikov  (was: Ilya Borisov)

[~anovikov], please review. I've decided to go with a second option. Supported 
browsers are as follows: IE11, Chrome last 18 months, Firefox last 18 months, 
Safari 10+, Edge last 6 months. IE11 and Safari choices are based on what I was 
told before as minimal supported versions. Chrome, Firefox and Edge have 
generally very lax requirements.

> Web console: some error messages are too technical
> --
>
> Key: IGNITE-6873
> URL: https://issues.apache.org/jira/browse/IGNITE-6873
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
> Environment: Chrome 29
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Minor
>
> *What happens:*
> Chrome 29 throws an error about missing {{atob}} and {{btoa}} global 
> functions (used in the frontend AgentManager service). The error gets 
> succesfully displayed to user in a default error notification, but ambiguous 
> message "Reference error: can't find atob" provides very little useful info 
> for most of users without advanced JS background.
> *What should happen:*
> Web console should relay this and similar errors in a more accessible manner.
> *Possible solutions:*
> 1. Consider missing API errors as operational, add explicit handler to 
> generate better messages, detect features and polyfill when possible. Pros: 
> better UX, increases supported browsers percentage. Cons: very high 
> maintenance cost.
> 2. Notify user about unsupported/outdated browser. Pros: easy to implement, 
> simultaneously covers lots of potential issues. Cons: very non-specific, UX 
> worse than option #1.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov closed IGNITE-6824.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6859) Web console: does not work in IE11

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov closed IGNITE-6859.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web console: does not work in IE11
> --
>
> Key: IGNITE-6859
> URL: https://issues.apache.org/jira/browse/IGNITE-6859
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
> Environment: WIndows 10, IE11
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> *What happens:*
> Web console does not work in IE11 at all, it gets stuck at loading screen 
> indefinitely and logs an error into console.
> *Expected behavior:*
> Web console should work in IE11.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6873) Web console: some error messages are too technical

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-6873:


 Summary: Web console: some error messages are too technical
 Key: IGNITE-6873
 URL: https://issues.apache.org/jira/browse/IGNITE-6873
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: wizards
 Environment: Chrome 29
Reporter: Ilya Borisov
Assignee: Ilya Borisov
Priority: Minor


*What happens:*
Chrome 29 throws an error about missing {{atob}} and {{btoa}} global functions 
(used in the frontend AgentManager service). The error gets succesfully 
displayed to user in a default error notification, but ambiguous message 
"Reference error: can't find atob" provides very little useful info for most of 
users without advanced JS background.

*What should happen:*
Web console should relay this and similar errors in a more accessible manner.

*Possible solutions:*
1. Consider missing API errors as operational, add explicit handler to generate 
better messages, detect features and polyfill when possible. Pros: better UX, 
increases supported browsers percentage. Cons: very high maintenance cost.
2. Notify user about unsupported/outdated browser. Pros: easy to implement, 
simultaneously covers lots of potential issues. Cons: very non-specific, UX 
worse than option #1.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Borisov reassigned IGNITE-6824:


Assignee: Andrey Novikov  (was: Pavel Konstantinov)

[~anovikov] please review.

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5635) Web Console: Show query execution progress

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-5635:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Issue with false indication fixed. Please test

> Web Console: Show query execution progress
> --
>
> Key: IGNITE-5635
> URL: https://issues.apache.org/jira/browse/IGNITE-5635
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> Show query execution progress, some progress or spinning wheel.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Borisov reassigned IGNITE-6824:


Assignee: Pavel Konstantinov  (was: Ilya Borisov)

[~pkonstantinov] I've fixed the step validator issue on basic configure page, 
please test.

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249074#comment-16249074
 ] 

Ilya Borisov edited comment on IGNITE-6824 at 11/13/17 3:34 AM:


pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused [new step validator on 
input[type='number']|"https://docs.angularjs.org/guide/migration#-input-type-number-;].


was (Author: klaster_1):
pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused [new step validator on 
input[type='number']|https://docs.angularjs.org/guide/migration#-input-type-number-].

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249074#comment-16249074
 ] 

Ilya Borisov edited comment on IGNITE-6824 at 11/13/17 3:34 AM:


pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused new step validator on 
input[type='number']([https://docs.angularjs.org/guide/migration#-input-type-number-]).


was (Author: klaster_1):
pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused [new step validator on 
input[type='number']|"https://docs.angularjs.org/guide/migration#-input-type-number-;].

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249074#comment-16249074
 ] 

Ilya Borisov edited comment on IGNITE-6824 at 11/13/17 3:33 AM:


pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused [new step validator on 
input[type='number']|https://docs.angularjs.org/guide/migration#-input-type-number-].


was (Author: klaster_1):
pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused [new step validator on 
input[type='number']](https://docs.angularjs.org/guide/migration#-input-type-number-).

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Borisov reopened IGNITE-6824:
--
  Assignee: Ilya Borisov  (was: Pavel Konstantinov)

pcbScaleNumber directive on basic configuration page shows validation error 
without any message. The issue is caused [new step validator on 
input[type='number']](https://docs.angularjs.org/guide/migration#-input-type-number-).

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249073#comment-16249073
 ] 

Pavel Konstantinov commented on IGNITE-6824:


Basic configuration screen 
-   Validation doesn't work in Off-heap size field



> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4939) Receive event before cache initialized

[Alexandr Kuramshin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248934#comment-16248934
 ] 

Alexandr Kuramshin commented on IGNITE-4939:


Was reproduced recently on TC 
https://ci.ignite.apache.org/viewLog.html?buildId=939024=buildResultsDiv=Ignite20Tests_IgniteBinarySImpleMapperBasic#testNameId-8143606663834956785

> Receive event before cache initialized
> --
>
> Key: IGNITE-4939
> URL: https://issues.apache.org/jira/browse/IGNITE-4939
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: Nikolay Tikhonov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.1
>
>
> Receive event before cache initialized that leads to the following:
> {noformat}
> Exception in thread "sys-#755%Default%" java.lang.IllegalArgumentException: 
> Cache is not configured: ignite-sys-cache
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3343)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:719)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:691)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1086)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2332)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1042)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:1011)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[Alexandr Kuramshin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandr Kuramshin updated IGNITE-79:
-
Fix Version/s: 2.4

> Illegal state exception in affinity assignment cache
> 
>
> Key: IGNITE-79
> URL: https://issues.apache.org/jira/browse/IGNITE-79
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Yakov Zhdanov
> Fix For: 2.4
>
> Attachments: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log
>
>
> {noformat}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated 
> [locNodeId=41caf5c2-3827-4566-9e52-22dabf51f864, topVer=179, head=180]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:328)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:294)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:349)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:478)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool$ExchangeWorker.body(GridDhtPartitionDemandPool.java:1285)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:151) 
> ~[gridgain-core-6.2.1-p1.jar:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-79) Illegal state exception in affinity assignment cache

[Alexandr Kuramshin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandr Kuramshin reassigned IGNITE-79:


Assignee: Stanilovsky Evgeny

> Illegal state exception in affinity assignment cache
> 
>
> Key: IGNITE-79
> URL: https://issues.apache.org/jira/browse/IGNITE-79
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Yakov Zhdanov
>Assignee: Stanilovsky Evgeny
> Fix For: 2.4
>
> Attachments: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log
>
>
> {noformat}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated 
> [locNodeId=41caf5c2-3827-4566-9e52-22dabf51f864, topVer=179, head=180]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:328)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:294)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:349)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:478)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool$ExchangeWorker.body(GridDhtPartitionDemandPool.java:1285)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:151) 
> ~[gridgain-core-6.2.1-p1.jar:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[Alexandr Kuramshin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandr Kuramshin updated IGNITE-79:
-
Attachment: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log

> Illegal state exception in affinity assignment cache
> 
>
> Key: IGNITE-79
> URL: https://issues.apache.org/jira/browse/IGNITE-79
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Yakov Zhdanov
>Assignee: Stanilovsky Evgeny
> Fix For: 2.4
>
> Attachments: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log
>
>
> {noformat}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated 
> [locNodeId=41caf5c2-3827-4566-9e52-22dabf51f864, topVer=179, head=180]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:328)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:294)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:349)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:478)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool$ExchangeWorker.body(GridDhtPartitionDemandPool.java:1285)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:151) 
> ~[gridgain-core-6.2.1-p1.jar:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-79) Illegal state exception in affinity assignment cache

[Alexandr Kuramshin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248925#comment-16248925
 ] 

Alexandr Kuramshin commented on IGNITE-79:
--

Recently reproduced with {{GridServiceProcessorMultiNodeConfigSelfTest}}. 
Running the whole test class {{testAll()}} fails frequently but not always. 
This is the cause the test looks flaky on TC.

Log right before an error

{noformat}
[2017-11-11 23:33:34,689][WARN 
][tcp-disco-msg-worker-#3%service.GridServiceProcessorMultiNodeConfigSelfTest0%][TcpDiscoverySpi]
 Failing client node due to not receiving metrics updates from client node 
within 'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing 
configuration property) [timeout=1, node=TcpDiscoveryNode 
[id=a3768cec-1275-46a7-aefa-afc23816, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
192.168.1.111], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
akuramshinpc.lan/192.168.1.111:0], discPort=0, order=11, intOrder=9, 
lastExchangeTime=1510418004405, loc=false, ver=2.3.0#19700101-sha1:, 
isClient=true]]
[2017-11-11 23:33:34,692][WARN 
][disco-event-worker-#36%service.GridServiceProcessorMultiNodeConfigSelfTest0%][GridDiscoveryManager]
 Node FAILED: TcpDiscoveryNode [id=a3768cec-1275-46a7-aefa-afc23816, 
addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 192.168.1.111], 
sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, akuramshinpc.lan/192.168.1.111:0], 
discPort=0, order=11, intOrder=9, lastExchangeTime=1510418004405, loc=false, 
ver=2.3.0#19700101-sha1:, isClient=true]
[2017-11-11 23:33:34,699][INFO 
][disco-event-worker-#84%service.GridServiceProcessorMultiNodeConfigSelfTest1%][GridDiscoveryManager]
 Topology snapshot [ver=17, servers=5, clients=0, CPUs=8, heap=7.1GB]
[2017-11-11 23:33:35,605][INFO 
][srvc-deploy-#39%service.GridServiceProcessorMultiNodeConfigSelfTest0%][GridServiceProcessor]
 Service processor detected a topology change during assignments calculation 
(will abort current iteration and re-calculate on the newer version): 
[topVer=AffinityTopologyVersion [topVer=15, minorTopVer=0], 
newTopVer=AffinityTopologyVersion [topVer=17, minorTopVer=0]]
[2017-11-11 
23:33:35,644][ERROR][srvc-deploy-#165%service.GridServiceProcessorMultiNodeConfigSelfTest2%][GridServiceProcessor]
 Error when executing service: null
{noformat}

Stack trace after 

{noformat}
java.lang.IllegalStateException: Getting affinity for topology version earlier 
than affinity is calculated [locNode=TcpDiscoveryNode 
[id=be7e8aae-54b4-419e-94c6-d8eaaaf2, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3, 
lastExchangeTime=1510418014692, loc=true, ver=2.3.0#19700101-sha1:, 
isClient=false], grp=ignite-sys-cache, topVer=AffinityTopologyVersion 
[topVer=16, minorTopVer=0], head=AffinityTopologyVersion [topVer=17, 
minorTopVer=0], history=[AffinityTopologyVersion [topVer=3, minorTopVer=0], 
AffinityTopologyVersion [topVer=4, minorTopVer=0], AffinityTopologyVersion 
[topVer=5, minorTopVer=0], AffinityTopologyVersion [topVer=6, minorTopVer=0], 
AffinityTopologyVersion [topVer=7, minorTopVer=0], AffinityTopologyVersion 
[topVer=8, minorTopVer=0], AffinityTopologyVersion [topVer=9, minorTopVer=0], 
AffinityTopologyVersion [topVer=10, minorTopVer=0], AffinityTopologyVersion 
[topVer=11, minorTopVer=0], AffinityTopologyVersion [topVer=12, minorTopVer=0], 
AffinityTopologyVersion [topVer=13, minorTopVer=0], AffinityTopologyVersion 
[topVer=14, minorTopVer=0], AffinityTopologyVersion [topVer=15, minorTopVer=0], 
AffinityTopologyVersion [topVer=17, minorTopVer=0]]]
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:519)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:419)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:220)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:256)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:247)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:271)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1789)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:1976)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
{noformat}

> Illegal state exception in affinity 

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[Alexandr Kuramshin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandr Kuramshin updated IGNITE-79:
-
Affects Version/s: 2.3

> Illegal state exception in affinity assignment cache
> 
>
> Key: IGNITE-79
> URL: https://issues.apache.org/jira/browse/IGNITE-79
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Yakov Zhdanov
>
> {noformat}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated 
> [locNodeId=41caf5c2-3827-4566-9e52-22dabf51f864, topVer=179, head=180]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:328)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:294)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:349)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:478)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool$ExchangeWorker.body(GridDhtPartitionDemandPool.java:1285)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:151) 
> ~[gridgain-core-6.2.1-p1.jar:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6802) NullPointerException when WAL store and WAL archive paths are same

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248843#comment-16248843
 ] 

ASF GitHub Bot commented on IGNITE-6802:


GitHub user SomeFire opened a pull request:

https://github.com/apache/ignite/pull/3021

IGNITE-6802

Throwing meaningful exception.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/SomeFire/ignite IGNITE-6802

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3021.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3021


commit c12b5b247cfb5c0ea5d45fab2f97fc53cf71da51
Author: Dmitrii Ryabov 
Date:   2017-11-12T12:36:14Z

IGNITE-6802: test

commit d2cd6412d295789c588438950c1e7fa5833e341d
Author: Dmitrii Ryabov 
Date:   2017-11-12T12:38:02Z

IGNITE-6802: throwing meaningful exception




> NullPointerException when WAL store and WAL archive paths are same 
> ---
>
> Key: IGNITE-6802
> URL: https://issues.apache.org/jira/browse/IGNITE-6802
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.2
>Reporter: Alexey Kukushkin
>Assignee: Ryabov Dmitrii
>  Labels: newbie, usability
> Fix For: 2.4
>
>
> Configuring WAL store and WAL archive paths to be the same results in 
> NullPointerException. We should display a meaningful error about the 
> misconfiguration instead.
> See 
> http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-in-FileWriteAheadLogManager-java-1313-tc17860.html
> The thread includes the reproducer code and stack trace. I was able to 
> reproduce the issue with today's (31-Oct-2017) Apache master.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)