[jira] [Commented] (IGNITE-3536) IGFS: Implement async methods for all base file system operations.

2017-04-15 Thread Alexei Kaigorodov (JIRA)

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

Alexei Kaigorodov commented on IGNITE-3536:
---

do we have examples of user tasks which can be solved with async IGFS API?

> IGFS: Implement async methods for all base file system operations.
> --
>
> Key: IGNITE-3536
> URL: https://issues.apache.org/jira/browse/IGNITE-3536
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Alexei Kaigorodov
> Fix For: 2.1
>
>
> 1) Remove {{IgniteAsyncSupport}} interface
> 2) Implement async counterparts for all FS operations.
> Justification: some structure file system operations might be very 
> time-consuming, so having async counterparts sounds like a good idea.
> The questions is what thread pool will host these tasks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Comment Edited] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

2017-04-15 Thread Valentin Kulichenko (JIRA)

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

Valentin Kulichenko edited comment on IGNITE-4949 at 4/15/17 9:55 AM:
--

[~DmitriyGovorukhin], is there a pull request that I can take a look at?


was (Author: vkulichenko):
[~DmitriyGovorukhin], is there a pull-request that I can take a look at?

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

2017-04-15 Thread Valentin Kulichenko (JIRA)

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

Valentin Kulichenko commented on IGNITE-4949:
-

[~DmitriyGovorukhin], is there a pull-request that I can take a look at?

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

2017-04-15 Thread Dmitriy Govorukhin (JIRA)

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

Dmitriy Govorukhin commented on IGNITE-4949:


[~vkulichenko] Done, please look 
[pull/1803|https://github.com/apache/ignite/pull/1803]

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

2017-04-15 Thread Valentin Kulichenko (JIRA)

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

Valentin Kulichenko commented on IGNITE-4949:
-

[~DmitriyGovorukhin], it looks like this change makes sure that binary mapping 
comes first, which makes sense. But why do we still need the second mapping?

[~kuaw26], I think you should take a look at this as well, because you know 
implementation details of the POJO store much better.

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4953) Rework logic of concurrent schema changes

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov commented on IGNITE-4953:
-

[~al.psc],
Please see my branch {{ignite-4953-1}} where I polished several problems during 
review. However, it doesn't work still. The problem is that H2 knows nothing 
about indexes created on table initialization phase. For this reason 
{{DynamicIndexBasicClientSelfTest.testDrop}} fails with {{Index "IDX_1" not 
found}} exception thrown from H2 internals.

> Rework logic of concurrent schema changes
> -
>
> Key: IGNITE-4953
> URL: https://issues.apache.org/jira/browse/IGNITE-4953
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.0
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>
> H2's prepared statements store references to indexes that were present when 
> the statement was parsed and initialized - this means that currently there's 
> no way to prevent index usage if it goes down between the moment when the 
> statement is created and actually executed. Have to come up with some new 
> locking schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4953) Rework logic of concurrent schema changes

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov commented on IGNITE-4953:
-

Another problem is that we use old {{GridH2TreeIndex}}, while new 
{{H2TreeIndex}} should be used instead.

> Rework logic of concurrent schema changes
> -
>
> Key: IGNITE-4953
> URL: https://issues.apache.org/jira/browse/IGNITE-4953
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.0
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>
> H2's prepared statements store references to indexes that were present when 
> the statement was parsed and initialized - this means that currently there's 
> no way to prevent index usage if it goes down between the moment when the 
> statement is created and actually executed. Have to come up with some new 
> locking schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (IGNITE-4994) Restore GridH2TableSelfTest

2017-04-15 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-4994:
---

 Summary: Restore GridH2TableSelfTest
 Key: IGNITE-4994
 URL: https://issues.apache.org/jira/browse/IGNITE-4994
 Project: Ignite
  Issue Type: Task
  Components: SQL
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


Test is broken after recent refactoring due to DDL feature. Need to restore it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4953) Rework logic of concurrent schema changes

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov commented on IGNITE-4953:
-

Fixed. Data consistency is fine. However, there are some weird failures in 
{{H2DynamicIndexSelfTest}} still.

> Rework logic of concurrent schema changes
> -
>
> Key: IGNITE-4953
> URL: https://issues.apache.org/jira/browse/IGNITE-4953
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.0
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>
> H2's prepared statements store references to indexes that were present when 
> the statement was parsed and initialized - this means that currently there's 
> no way to prevent index usage if it goes down between the moment when the 
> statement is created and actually executed. Have to come up with some new 
> locking schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (IGNITE-4953) Rework logic of concurrent schema changes

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov reassigned IGNITE-4953:
---

Resolution: Fixed
  Assignee: Vladimir Ozerov  (was: Alexander Paschenko)

> Rework logic of concurrent schema changes
> -
>
> Key: IGNITE-4953
> URL: https://issues.apache.org/jira/browse/IGNITE-4953
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.0
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> H2's prepared statements store references to indexes that were present when 
> the statement was parsed and initialized - this means that currently there's 
> no way to prevent index usage if it goes down between the moment when the 
> statement is created and actually executed. Have to come up with some new 
> locking schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Issue Comment Deleted] (IGNITE-4565) Support CREATE INDEX DDL statements

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov updated IGNITE-4565:

Comment: was deleted

(was: GitHub user devozerov opened a pull request:

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

IGNITE-4565



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4565

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

https://github.com/apache/ignite/pull/1773.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 #1773


commit fcadf67cf134d603f4b8c9364ab4584cc40efed6
Author: devozerov 
Date:   2017-02-02T08:54:10Z

IGNITE-4570: DDL parsing.

commit 796c933ac70d75f4f642f5b351abc762effd
Author: devozerov 
Date:   2017-03-02T11:29:53Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

commit c05be524a9b73356d26474aa9962434155d111f3
Author: Alexander Paschenko 
Date:   2017-03-03T10:55:41Z

IGNITE-4633 Introduced component type for DDL statements processor.

commit f79ead47a895eb6d205ea0f2a813efb23b67c989
Author: Alexander Paschenko 
Date:   2017-03-03T11:57:10Z

IGNITE-4635: Introduced DDL worker thread.

commit d97716ef9024aea562899d0b8b17c32c49e41f4b
Author: devozerov 
Date:   2017-03-03T12:40:00Z

Added schema version.

commit 19f0568f4653dfcace6148ded0bd357e4be65a48
Author: devozerov 
Date:   2017-03-09T08:06:38Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

commit f6fa2659d88994f7942f1ac5e1fff65e697ac541
Author: devozerov 
Date:   2017-03-09T11:05:27Z

Creating correct path for index create.

commit f4a56fe67739ca6b8666cec6c0b2f7bce288d191
Author: devozerov 
Date:   2017-03-09T11:31:17Z

Moved full-text index into separate property.

commit 157db2b6bfd40a76af3ee695665fe9c6c4a4b54e
Author: devozerov 
Date:   2017-03-09T12:04:09Z

Removed unnecessary GridQueryIndexType.

commit d8d2ad8f93efedd4787ec04a9886b28266f7ac8d
Author: devozerov 
Date:   2017-03-09T12:32:28Z

WIP on general wire-up.

commit fc2cf15fd31ebfb05052bf297aeaec959d61af1e
Author: devozerov 
Date:   2017-03-09T13:07:42Z

Started working on disco messages.

commit 0721eb98f5c856afb8e4bbd3607c4d00492f8ff9
Author: devozerov 
Date:   2017-03-09T13:11:07Z

Minors.

commit 323f77545e30ebfde00b81a741546914dd18b283
Author: devozerov 
Date:   2017-03-09T13:26:29Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/configuration/CacheConfiguration.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/query/GridCacheQueryManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/ddl/DdlTask.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GridLuceneIndex.java

commit be88fa26f86e31c0ef562f9484412dde684327ef
Author: devozerov 
Date:   2017-03-09T13:49:26Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java

commit 539f1d84063c731460bb18bf59a0602c27482d22
Author: devozerov 
Date:   2017-03-09T13:50:37Z

Minors.

commit 752e71490b79f27fb182353ae7c7babb84f0b0fd
Author: devozerov 
Date:   2017-03-09T13:53:54Z

Minors.

commit 20bd9eddaacfa05c5a4db3d951fda544d53d5410
Author: devozerov 
Date:   2017-03-09T14:00:11Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java

commit a4d01a632506b82a1cedb9538a843229feb543be
Author: devozerov 
Date:   2017-03-09T14:03:38Z

Finished refactoring.

commit 9622039a540957ef73f558dbc99da0dbe88f38da
Author: devozerov 
Date:   2017-03-09T14:28:14Z

WIP.

commit 318ddedafc810fefdba12ac2334ac467c746dc04
Author: devozerov 
Date:   2017-03-09T14:31:53Z

WIP.

commit 9e32da96efb1cef44c81a360e35a494715b6483b
Author: devozerov 
Date:   2017-03-09T14:54:37Z

WIP.

commit cd477c039a082eb37e10848cb3aee71c01c01e20
Author: devozerov 
Date:   2017-03-09T15:05:21Z

WIP.

commit abf2f3389ee9036039be58a1e3b18c30d52a8f20
Author: devozerov 
Date:   2017-03-09T15:12:12Z

Minors.

commit e316c4b7464c11ef4eeb7a1a2509e897f67961f5
Author: devozerov 
Date:   2017-03-10T08:11:04Z

WIP on client future handling.

commit 6a7aace9c813490fb49a87221d0a96564949600e
Author: devozerov 
Date:   2017-03-10T08:12:09Z

Minors.

commit 8ddd3de1dda064d14bb14a2e7cb9661e41da72f5
Author: dev

[jira] [Issue Comment Deleted] (IGNITE-4565) Support CREATE INDEX DDL statements

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov updated IGNITE-4565:

Comment: was deleted

(was: Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/1773
)

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4565) Support CREATE INDEX DDL statements

2017-04-15 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on IGNITE-4565:


Github user devozerov closed the pull request at:

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


> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-4565) Support CREATE INDEX DDL statements

2017-04-15 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on IGNITE-4565:


GitHub user devozerov opened a pull request:

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

IGNITE-4565



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4565

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

https://github.com/apache/ignite/pull/1804.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 #1804


commit fcadf67cf134d603f4b8c9364ab4584cc40efed6
Author: devozerov 
Date:   2017-02-02T08:54:10Z

IGNITE-4570: DDL parsing.

commit 796c933ac70d75f4f642f5b351abc762effd
Author: devozerov 
Date:   2017-03-02T11:29:53Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

commit c05be524a9b73356d26474aa9962434155d111f3
Author: Alexander Paschenko 
Date:   2017-03-03T10:55:41Z

IGNITE-4633 Introduced component type for DDL statements processor.

commit f79ead47a895eb6d205ea0f2a813efb23b67c989
Author: Alexander Paschenko 
Date:   2017-03-03T11:57:10Z

IGNITE-4635: Introduced DDL worker thread.

commit d97716ef9024aea562899d0b8b17c32c49e41f4b
Author: devozerov 
Date:   2017-03-03T12:40:00Z

Added schema version.

commit 19f0568f4653dfcace6148ded0bd357e4be65a48
Author: devozerov 
Date:   2017-03-09T08:06:38Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

commit f6fa2659d88994f7942f1ac5e1fff65e697ac541
Author: devozerov 
Date:   2017-03-09T11:05:27Z

Creating correct path for index create.

commit f4a56fe67739ca6b8666cec6c0b2f7bce288d191
Author: devozerov 
Date:   2017-03-09T11:31:17Z

Moved full-text index into separate property.

commit 157db2b6bfd40a76af3ee695665fe9c6c4a4b54e
Author: devozerov 
Date:   2017-03-09T12:04:09Z

Removed unnecessary GridQueryIndexType.

commit d8d2ad8f93efedd4787ec04a9886b28266f7ac8d
Author: devozerov 
Date:   2017-03-09T12:32:28Z

WIP on general wire-up.

commit fc2cf15fd31ebfb05052bf297aeaec959d61af1e
Author: devozerov 
Date:   2017-03-09T13:07:42Z

Started working on disco messages.

commit 0721eb98f5c856afb8e4bbd3607c4d00492f8ff9
Author: devozerov 
Date:   2017-03-09T13:11:07Z

Minors.

commit 323f77545e30ebfde00b81a741546914dd18b283
Author: devozerov 
Date:   2017-03-09T13:26:29Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/configuration/CacheConfiguration.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/query/GridCacheQueryManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/ddl/DdlTask.java
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GridLuceneIndex.java

commit be88fa26f86e31c0ef562f9484412dde684327ef
Author: devozerov 
Date:   2017-03-09T13:49:26Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java

commit 539f1d84063c731460bb18bf59a0602c27482d22
Author: devozerov 
Date:   2017-03-09T13:50:37Z

Minors.

commit 752e71490b79f27fb182353ae7c7babb84f0b0fd
Author: devozerov 
Date:   2017-03-09T13:53:54Z

Minors.

commit 20bd9eddaacfa05c5a4db3d951fda544d53d5410
Author: devozerov 
Date:   2017-03-09T14:00:11Z

Merge branch 'ignite-2.0' into ignite-4565-ddl

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java

commit a4d01a632506b82a1cedb9538a843229feb543be
Author: devozerov 
Date:   2017-03-09T14:03:38Z

Finished refactoring.

commit 9622039a540957ef73f558dbc99da0dbe88f38da
Author: devozerov 
Date:   2017-03-09T14:28:14Z

WIP.

commit 318ddedafc810fefdba12ac2334ac467c746dc04
Author: devozerov 
Date:   2017-03-09T14:31:53Z

WIP.

commit 9e32da96efb1cef44c81a360e35a494715b6483b
Author: devozerov 
Date:   2017-03-09T14:54:37Z

WIP.

commit cd477c039a082eb37e10848cb3aee71c01c01e20
Author: devozerov 
Date:   2017-03-09T15:05:21Z

WIP.

commit abf2f3389ee9036039be58a1e3b18c30d52a8f20
Author: devozerov 
Date:   2017-03-09T15:12:12Z

Minors.

commit e316c4b7464c11ef4eeb7a1a2509e897f67961f5
Author: devozerov 
Date:   2017-03-10T08:11:04Z

WIP on client future handling.

commit 6a7aace9c813490fb49a87221d0a96564949600e
Author: devozerov 
Date:   2017-03-10T08:12:09Z

Minors.

commit 8ddd3de1dda064d14bb14a2e7cb9

[jira] [Comment Edited] (IGNITE-4565) Support CREATE INDEX DDL statements

2017-04-15 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov edited comment on IGNITE-4565 at 4/15/17 3:15 PM:
--

Outstanding issues:
1) Fix client reconnect schema consistency issue
2) Additional test for local cache, replicated cache, near+dht and near caches
3) Add rebalance consistency tests


was (Author: vozerov):
Outstanding issues:
1) Fix client reconnect schema consistency issue
2) Fix DROP INDEX data consistency issue (+ add more concurrent data tests).
3) Additional test for local cache, replicated cache, near+dht and near caches.

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)