[jira] [Commented] (IGNITE-4027) Extract PlatformTargetProxy interface

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4027:


You are correct. Main entry point is PlatformTarget, and there are no 
future-related methods in it.

PlatformTargetProxy and PlatformAsyncTarget still have future-related methods 
for legacy reasons, they will be removed as part of IGNITE-4177.

> Extract PlatformTargetProxy interface
> -
>
> Key: IGNITE-4027
> URL: https://issues.apache.org/jira/browse/IGNITE-4027
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> PlatformTarget interface contains methods that are called from JNI. These 
> methods operate on internal things like memory pointers.
> PlatformAbstractTarget creates streams & readers and calls paired protected 
> methods.
> We need to separate the part with streams/readers from the part with pointers 
> via an additional interface:
> * PlatformTargetProxy will be invoked from JNI
> * PlatformTarget will contain only "nice" methods and will be invoked by 
> PlatformTargetProxy implementation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4177) .NET: Remove PlatformAsyncTarget and remove future-related code from PlatformTargetProxy

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4177:
--

 Summary: .NET: Remove PlatformAsyncTarget and remove 
future-related code from PlatformTargetProxy
 Key: IGNITE-4177
 URL: https://issues.apache.org/jira/browse/IGNITE-4177
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0


* PlatformAsyncTarget supports legacy async mechanism and should be removed.

* PlatformTargetProxy supports legacy mode via the following methods, remove 
them:
{code}
void listenFuture(final long futId, int typ) throws Exception;
void listenFutureForOperation(final long futId, int typ, int opId) throws 
Exception;
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-3066) Set of Redis commands that can be easily implemented via existing REST commands

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-3066 at 11/7/16 7:20 AM:
---

Roman, see my first comments:

# In modules\clients\pom.xml new dependency "redis.clients.jedis" should be 
test.
# Please revert changes in javadocs in {{IgniteConfiguration}} & 
{{GridKernalContext}}, they are not related to this issue.
# {{GridRedisGenericException}} & {{GridRedisTypeException}} - ASF header 
missing.
# {{GridClientPacketType}} - may be it will be better to have {{REDIS}} instead 
of {{RESP}}?
# {{RedisProtocolSelfTest}} move {{private static final int GRID_CNT = 1}} 
constant to the class top. Also this constant is "1".
 What about multi nodes tests?
# {{GridRedisGenericException}} - how about to introduce several descendants? 
Like {{GridRedisIllegalArgumentException}}?
# {{GridRedisTypeException }}- declared, but I not found any {{throw new 
GridRedisTypeException}}
# There a lot of duplicated code in 
{{GridRedisXXXCommandHandler.asRestRequest()}} methods - could this be somehow 
generalized in parent class?
  For example: {{GridRedisDelCommandHandler}} and 
{{GridRedisExistsCommandHandler}}.

I will do one more review after you will address my comments.


was (Author: kuaw26):
Roman, see my first comments:

# In modules\clients\pom.xml new dependency "redis.clients.jedis" should be 
test.
# Please revert changes in javadocs in {{IgniteConfiguration}} & 
{{GridKernalContext}}, they are not related to this issue.
# {{GridRedisGenericException}} & {{GridRedisTypeException}} - ASF header 
missing.
# {{GridClientPacketType}} - may be it will be better to have {{REDIS}} instead 
of {{RESP}}?
# {{RedisProtocolSelfTest}} move {{private static final int GRID_CNT = 1}} 
constant to the class top. Also this constant is "1".
 What about multi nodes tests?
# {{GridRedisGenericException}} - how about to introduce several descendants? 
Like {{GridRedisIllegalArgumentException}}?
# {{GridRedisTypeException }}- declared, but I not found any {{throw new 
GridRedisTypeException}}
# There a lot of duplicated code in 
{{GridRedisXXXCommandHandler.asRestRequest()}} methods - could this be somehow 
generalized in parent class?
  For example: {{GridRedisDelCommandHandler}} and 
{{GridRedisExistsCommandHandler}}.

I will do one more review after

> Set of Redis commands that can be easily implemented via existing REST 
> commands
> ---
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented 
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3066) Set of Redis commands that can be easily implemented via existing REST commands

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-3066:
--

Roman, see my first comments:

# In modules\clients\pom.xml new dependency "redis.clients.jedis" should be 
test.
# Please revert changes in javadocs in {{IgniteConfiguration}} & 
{{GridKernalContext}}, they are not related to this issue.
# {{GridRedisGenericException}} & {{GridRedisTypeException}} - ASF header 
missing.
# {{GridClientPacketType}} - may be it will be better to have {{REDIS}} instead 
of {{RESP}}?
# {{RedisProtocolSelfTest}} move {{private static final int GRID_CNT = 1}} 
constant to the class top. Also this constant is "1".
 What about multi nodes tests?
# {{GridRedisGenericException}} - how about to introduce several descendants? 
Like {{GridRedisIllegalArgumentException}}?
# {{GridRedisTypeException }}- declared, but I not found any {{throw new 
GridRedisTypeException}}
# There a lot of duplicated code in 
{{GridRedisXXXCommandHandler.asRestRequest()}} methods - could this be somehow 
generalized in parent class?
  For example: {{GridRedisDelCommandHandler}} and 
{{GridRedisExistsCommandHandler}}.

I will do one more review after

> Set of Redis commands that can be easily implemented via existing REST 
> commands
> ---
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented 
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4163) Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-4163:
--
Attachment: (was: IGNITE_4163_Fixed_ordering_of_row_numbers_.patch)

> Wrong SQL generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
> 
>
> Key: IGNITE-4163
> URL: https://issues.apache.org/jira/browse/IGNITE-4163
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Anghel Botos
>Assignee: Alexey Kuznetsov
> Attachments: IGNITE_4163_Oracle_specific_for_load_range_query_.patch
>
>
> The SQL statement generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
>  looks like this:
> {{SELECT KEY_COLUMN_1,KEY_COLUMN_2 FROM (SELECT KEY_COLUMN_1,KEY_COLUMN_2, 
> ROWNUM() AS rn FROM SOME_TABLE ORDER BY KEY_COLUMN_1,KEY_COLUMN_2) WHERE 
> mod(rn, ?) = 0}}
> For Oracle this is incorrect, as Oracle does not have a {{ROWNUM()}} 
> function. For the above query the following error is thrown: {{ORA-00923: 
> FROM keyword not found where expected}}
> Regarding row numbering Oracle has:
> * a {{ROWNUM}} pseudocolumn, in which case the query should have {{ROWNUM AS 
> rn}}
> * a {{ROW_NUMBER()}} function, in which case the query would become more 
> complicated. See 
> https://docs.oracle.com/database/121/SQLRF/functions170.htm#SQLRF06100 for 
> more details about {{ROW_NUMBER()}}
> Please make the neccessary adjustments to either {{BasicJdbcDialect}} or 
> {{OracleDialect}} so that a correct query is produced.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-3432) Multiple IGFS on the same caches.

[Taras Ledkov (JIRA)]

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

Taras Ledkov resolved IGNITE-3432.
--
Resolution: Fixed

> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
> Attachments: test2IGFS-client.xml, test2IGFS-server.xml
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes. 
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same 
> caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3066) Set of Redis commands that can be easily implemented via existing REST commands

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3066:


GitHub user shroman opened a pull request:

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

IGNITE-3066: Set of Redis commands that can be easily implemented via 
existing REST commands



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

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

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

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


commit 90fe51e356d8d7ac1fb9c11778e339a8cc41c400
Author: shtykh_roman 
Date:   2016-04-11T01:41:22Z

IGNITE-2788: Basic Redis protocol implementation.

commit 99115ee0f75debc7e7385265baf1689247cc0d39
Author: shtykh_roman 
Date:   2016-04-12T10:10:11Z

IGNITE-2788: Basic Redis protocol implementation. Reworked to run on REST 
server.

commit a450ae1872ce7cac9205a1614c74acc8edf04f5e
Author: shtykh_roman 
Date:   2016-04-13T09:43:30Z

IGNITE-2788: Basic Redis protocol implementation. GET command to see how 
cache commands work and more Redis return types.

commit 26d4c631a91bee233d054d0b322bbe6d3bdf698b
Author: shtykh_roman 
Date:   2016-04-14T09:42:44Z

IGNITE-2788: Basic Redis protocol implementation. Introduced a handler for 
string commands.

commit b3e7a2a5faf1799f304c18f85e934e0e85e55fbd
Author: shtykh_roman 
Date:   2016-04-15T11:39:07Z

IGNITE-2788: Basic Redis protocol implementation. Got rid of switch 
statements.

commit a3231a7d9338746ba2d25c8b6571b944a0f02556
Author: shtykh_roman 
Date:   2016-04-18T09:57:47Z

IGNITE-2788: Basic Redis protocol implementation. Introduced Redis protocol 
exceptions and added commands.

commit 998cf4da7ddbbb417d7f3fc6aa9b0c440e09d594
Author: shtykh_roman 
Date:   2016-04-19T03:59:38Z

IGNITE-2788: Basic Redis protocol implementation. Added STRLEN and GETSET 
commands.

commit 62d5cafed207c1a153f9e90fdaca801833e1999f
Author: shtykh_roman 
Date:   2016-04-27T08:09:14Z

IGNITE-2788: Basic Redis protocol implementation. Added SETRANGE and 
GETRANGE commands.

commit 127f459fae79f61fd0af81f7bd93a02b52f6c00b
Author: shtykh_roman 
Date:   2016-04-28T06:41:57Z

IGNITE-2788: Basic Redis protocol implementation. Added DEL, EXISTS and 
DBSIZE commands.

commit a8dae9d0090b53d9a409fb2985fe15ed76319a57
Author: shtykh_roman 
Date:   2016-11-01T03:07:18Z

IGNITE-2788: Moved handlers.

commit 0cd6723d2e413be61d31827a9f0444d4253a30ed
Author: shtykh_roman 
Date:   2016-11-07T04:28:04Z

Merge branch 'master' into ignite-2788




> Set of Redis commands that can be easily implemented via existing REST 
> commands
> ---
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented 
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4163) Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-4163:
--
Attachment: IGNITE_4163_Fixed_ordering_of_row_numbers_.patch

> Wrong SQL generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
> 
>
> Key: IGNITE-4163
> URL: https://issues.apache.org/jira/browse/IGNITE-4163
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Anghel Botos
>Assignee: Alexey Kuznetsov
> Attachments: IGNITE_4163_Fixed_ordering_of_row_numbers_.patch, 
> IGNITE_4163_Oracle_specific_for_load_range_query_.patch
>
>
> The SQL statement generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
>  looks like this:
> {{SELECT KEY_COLUMN_1,KEY_COLUMN_2 FROM (SELECT KEY_COLUMN_1,KEY_COLUMN_2, 
> ROWNUM() AS rn FROM SOME_TABLE ORDER BY KEY_COLUMN_1,KEY_COLUMN_2) WHERE 
> mod(rn, ?) = 0}}
> For Oracle this is incorrect, as Oracle does not have a {{ROWNUM()}} 
> function. For the above query the following error is thrown: {{ORA-00923: 
> FROM keyword not found where expected}}
> Regarding row numbering Oracle has:
> * a {{ROWNUM}} pseudocolumn, in which case the query should have {{ROWNUM AS 
> rn}}
> * a {{ROW_NUMBER()}} function, in which case the query would become more 
> complicated. See 
> https://docs.oracle.com/database/121/SQLRF/functions170.htm#SQLRF06100 for 
> more details about {{ROW_NUMBER()}}
> Please make the neccessary adjustments to either {{BasicJdbcDialect}} or 
> {{OracleDialect}} so that a correct query is produced.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4176) IgniteQueue not functioning as expected after remove().

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4176:


GitHub user amirakhmedov opened a pull request:

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

IGNITE-4176: IgniteQueue not functioning as expected after remove()



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

$ git pull https://github.com/amirakhmedov/ignite IGNITE-4176

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

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


commit cf89f6ea4ae24a770cf1b09ecb7bf582de2c113d
Author: Amir Akhmedov 
Date:   2016-11-07T04:07:19Z

IGNITE-4176: IgniteQueue not functioning as expected after remove()




> IgniteQueue not functioning as expected after remove().
> ---
>
> Key: IGNITE-4176
> URL: https://issues.apache.org/jira/browse/IGNITE-4176
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.7
>Reporter: C Saternos
>Assignee: Amir Akhmedov
> Fix For: 1.8
>
> Attachments: WhereDidItGo.java, pom.xml
>
>
> After removing an item from an IgniteQueue, the next item on the queue can be 
> viewed using peek().  However, poll() or take() does not retrieve the item.  
> When iterating through the remaining items in the queue, it appears that 1/2 
> of them are missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2712) Adjust width for cluster combobox on caches screen

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2712:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Adjust width for cluster combobox on caches screen
> --
>
> Key: IGNITE-2712
> URL: https://issues.apache.org/jira/browse/IGNITE-2712
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Trivial
>
> Create 11 clusters.
> Open Caches screen.
> Drop down clusters combobox.
> Currently in Firefox I see 'Select All ...'  but should 'Selected All (11)'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2712) Adjust width for cluster combobox on caches screen

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2712:
-
Assignee: (was: Maxim Afanasiev)

> Adjust width for cluster combobox on caches screen
> --
>
> Key: IGNITE-2712
> URL: https://issues.apache.org/jira/browse/IGNITE-2712
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Priority: Trivial
>
> Create 11 clusters.
> Open Caches screen.
> Drop down clusters combobox.
> Currently in Firefox I see 'Select All ...'  but should 'Selected All (11)'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2712) Adjust width for cluster combobox on caches screen

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2712:
-
Fix Version/s: (was: 1.8)

> Adjust width for cluster combobox on caches screen
> --
>
> Key: IGNITE-2712
> URL: https://issues.apache.org/jira/browse/IGNITE-2712
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Assignee: Maxim Afanasiev
>Priority: Trivial
>
> Create 11 clusters.
> Open Caches screen.
> Drop down clusters combobox.
> Currently in Firefox I see 'Select All ...'  but should 'Selected All (11)'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2278) Rework all tooltips - add bullets where multilines text

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2278:
-
Assignee: (was: Vasiliy Sisko)

> Rework all tooltips - add bullets where multilines text
> ---
>
> Key: IGNITE-2278
> URL: https://issues.apache.org/jira/browse/IGNITE-2278
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>
> We need to add bullets in tooltips where it make sense for better usability.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2984) Need to add validation that Alias and Index fields are present in Fields list

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2984:
-
Assignee: (was: Maxim Afanasiev)

> Need to add validation that Alias and Index fields are present in Fields list
> -
>
> Key: IGNITE-2984
> URL: https://issues.apache.org/jira/browse/IGNITE-2984
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2984) Need to add validation that Alias and Index fields are present in Fields list

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2984:
-
Fix Version/s: (was: 1.8)

> Need to add validation that Alias and Index fields are present in Fields list
> -
>
> Key: IGNITE-2984
> URL: https://issues.apache.org/jira/browse/IGNITE-2984
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Assignee: Maxim Afanasiev
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2072:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>
> Start tester
> select * from Person



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2072:
-
Assignee: (was: Andrey Novikov)

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>
> Start tester
> select * from Person



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3945) Web console: Implement configuration of DeploymentSpi

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3945:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Web console: Implement configuration of DeploymentSpi
> -
>
> Key: IGNITE-3945
> URL: https://issues.apache.org/jira/browse/IGNITE-3945
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3296) Validation fail in special case

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3296:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Validation fail in special case
> ---
>
> Key: IGNITE-3296
> URL: https://issues.apache.org/jira/browse/IGNITE-3296
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>
> # Enable some section that have disabled fields.
> # Input in field invalid value.
> # Disable section and try to save.
> - Validation show invalid message for disabled field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3296) Validation fail in special case

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3296:
-
Assignee: (was: Dmitriy Shabalin)

> Validation fail in special case
> ---
>
> Key: IGNITE-3296
> URL: https://issues.apache.org/jira/browse/IGNITE-3296
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>
> # Enable some section that have disabled fields.
> # Input in field invalid value.
> # Disable section and try to save.
> - Validation show invalid message for disabled field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3843) Web console: Not work basic validations.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3843:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Web console: Not work basic validations.
> 
>
> Key: IGNITE-3843
> URL: https://issues.apache.org/jira/browse/IGNITE-3843
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
>
> F.e. On cluster add empty Cache key configuration and try to save cluster.
> Also field with wrong value should be focused.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3296) Validation fail in special case

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3296:
-
Fix Version/s: (was: 1.8)

> Validation fail in special case
> ---
>
> Key: IGNITE-3296
> URL: https://issues.apache.org/jira/browse/IGNITE-3296
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>
> # Enable some section that have disabled fields.
> # Input in field invalid value.
> # Disable section and try to save.
> - Validation show invalid message for disabled field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3843) Web console: Not work basic validations.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3843:
-
Fix Version/s: (was: 1.8)

> Web console: Not work basic validations.
> 
>
> Key: IGNITE-3843
> URL: https://issues.apache.org/jira/browse/IGNITE-3843
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
>
> F.e. On cluster add empty Cache key configuration and try to save cluster.
> Also field with wrong value should be focused.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1765) Insufficient height for label of Y-axis in case of several Y-values

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1765:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Insufficient height for label of Y-axis in case of several Y-values
> ---
>
> Key: IGNITE-1765
> URL: https://issues.apache.org/jira/browse/IGNITE-1765
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
> Attachments: ig-1765.png
>
>
> Please see attachment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1766) Zooming of charts

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1766:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Zooming of charts
> -
>
> Key: IGNITE-1766
> URL: https://issues.apache.org/jira/browse/IGNITE-1766
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Attachments: ig-1766.png
>
>
> Currently the minimum results page size is 50, but in case of several values 
> on Y-axis viewing for example bar chart becomes uncomfortable (see attachment)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1483) Web console sign up via Google (i.e. via Google Identity Platform).

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1483:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Web console sign up via Google (i.e. via Google Identity Platform).
> ---
>
> Key: IGNITE-1483
> URL: https://issues.apache.org/jira/browse/IGNITE-1483
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Reporter: Nikita Ivanov
>
> Basically, why do we ask people to supply email, keep password or security 
> tokens when 99% of them have Google account already. Let's use Google 
> Identity Platform - https://developers.google.com/identity/ - for sign ins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1761) Load metadata from DB: add possibility to set JDBC driver jar file from local folder

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1761:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Load metadata from DB: add possibility to set JDBC driver jar file from local 
> folder
> 
>
> Key: IGNITE-1761
> URL: https://issues.apache.org/jira/browse/IGNITE-1761
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>
> Currently the list of available JDBC jar-files is configured only on 
> web-agent side by placing necessary files into 'jdbc-drivers' folder. In case 
> when user have not direct access to this folder he cannot place driver he 
> needed. So we need to give to user possibility to select needed JDBC driver 
> from local folder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1484) Allow to store configuration in Google Datastore.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1484:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Allow to store configuration in Google Datastore.
> -
>
> Key: IGNITE-1484
> URL: https://issues.apache.org/jira/browse/IGNITE-1484
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Reporter: Nikita Ivanov
>
> It would be very convenient to store a configuration (e.g. in Google 
> Datastore) and come back to it later. We need to introduce a notion of new 
> configuration (with a name) and ability to "load" previously saved 
> configuration by name.
> We should store these outside of local database so that it would survive 
> restarts and DB updates. Google Datastore is good tech to use here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4148) Web console: adding a first item in CheckpointSPI takes a long time under Firefox

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-4148:
-

Assignee: Vasiliy Sisko

> Web console: adding a first item in CheckpointSPI takes a long time under 
> Firefox
> -
>
> Key: IGNITE-4148
> URL: https://issues.apache.org/jira/browse/IGNITE-4148
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
>
> 1) I've noticed adding a first item in CheckpointSPI list takes a long time 
> in Firefox.
> We need to investigate and fix the reason.
> 2) Hide not mandatory fields under the 'show advanced' panel



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1736) Configuration add scroll to group from sidebar

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1736:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Configuration add scroll to group from sidebar
> --
>
> Key: IGNITE-1736
> URL: https://issues.apache.org/jira/browse/IGNITE-1736
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.5.0.final
>Reporter: Andrey Novikov
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1659) Add query history

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1659:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Add query history
> -
>
> Key: IGNITE-1659
> URL: https://issues.apache.org/jira/browse/IGNITE-1659
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>
> We need to implement saving query history and restoring query text into any 
> Query field.
> Note: currently we have workaround - we save notebooks with all queries in 
> it, but if user remove notebook he lost all queries from this notebook.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1212) Support different version of Ignite

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1212:
-
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Support different version of Ignite
> ---
>
> Key: IGNITE-1212
> URL: https://issues.apache.org/jira/browse/IGNITE-1212
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>
> Ignite configuration could evolve over time. Some new properties added, some 
> deprecated. We should add a dropdown with Ignite version in web UI that will 
> adjust list of available properties to show.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2055) Implement ability to select version

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2055:
-
Priority: Major  (was: Minor)

> Implement ability to select version 
> 
>
> Key: IGNITE-2055
> URL: https://issues.apache.org/jira/browse/IGNITE-2055
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Attachments: 7vQf7r8.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2055) Implement ability to select version

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2055:
-
Issue Type: Task  (was: Bug)

> Implement ability to select version 
> 
>
> Key: IGNITE-2055
> URL: https://issues.apache.org/jira/browse/IGNITE-2055
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Attachments: 7vQf7r8.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2055) Implement ability to select version

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2055:
-
Assignee: (was: Dmitriy Shabalin)

> Implement ability to select version 
> 
>
> Key: IGNITE-2055
> URL: https://issues.apache.org/jira/browse/IGNITE-2055
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
> Attachments: 7vQf7r8.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-868) Fix GridUpdateNotifierSelfTest.testNotifier

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-868:
--
Assignee: (was: Andrey Novikov)

> Fix GridUpdateNotifierSelfTest.testNotifier   
> 
>
> Key: IGNITE-868
> URL: https://issues.apache.org/jira/browse/IGNITE-868
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: sprint-5
>Reporter: Irina Vasilinets
> Fix For: 1.5.0.final
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2055) Implement ability to select version

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2055:
-
Priority: Minor  (was: Major)

> Implement ability to select version 
> 
>
> Key: IGNITE-2055
> URL: https://issues.apache.org/jira/browse/IGNITE-2055
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
>Priority: Minor
> Attachments: 7vQf7r8.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2055) Implement ability to select version

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2055:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Implement ability to select version 
> 
>
> Key: IGNITE-2055
> URL: https://issues.apache.org/jira/browse/IGNITE-2055
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Attachments: 7vQf7r8.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3730) Web Console: Add scan for near cache on SQL screen

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3730:
-
Fix Version/s: (was: 1.8)

> Web Console: Add scan for near cache on SQL screen
> --
>
> Key: IGNITE-3730
> URL: https://issues.apache.org/jira/browse/IGNITE-3730
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3721) Web Console: Improve usability of Domain model screen

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3721:
-
Fix Version/s: (was: 1.8)

> Web Console: Improve usability of Domain model screen
> -
>
> Key: IGNITE-3721
> URL: https://issues.apache.org/jira/browse/IGNITE-3721
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>
> Current implementation of Domain screen is not very usable:
> # Information is duplicated (query fields, db fields, aliases, indexes).
> # No way to configure affinity key.
> # No way to configure POJOs without cache store.
> # No way to configure without key field(s).
> Possible rework:
> We should have one section that will allow to work with fields and provide 
> optional: alias, mapping to DB, index, affinity.
> And group indexes could be a separate section.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3622) BinaryObject: print idHash in toString() method only in debug mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3622:
-
Fix Version/s: (was: 1.8)
   2.0

> BinaryObject: print idHash in toString() method only in debug mode
> --
>
> Key: IGNITE-3622
> URL: https://issues.apache.org/jira/browse/IGNITE-3622
> Project: Ignite
>  Issue Type: Task
>  Components: newbie
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Priority: Trivial
> Fix For: 2.0
>
>
> Current implementation of BinaryObject.toString() method print idHash for 
> internal objects, for example, for AffinityKey.
> This lead to "unstable" result of toString() method, you will get different 
> strings on each toString() invocation.
> Possible fix: introduce
> {code}
> private static final boolean debug = false;
> {code}
> And check this flag in toString().
> If some one will need idHash for debug reasons he could change this flag in 
> its private build and debug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3657) Add formatter for UUID fields

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3657:
-
Fix Version/s: (was: 1.8)

> Add formatter for UUID fields
> -
>
> Key: IGNITE-3657
> URL: https://issues.apache.org/jira/browse/IGNITE-3657
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
>
> Currently it is very hard to input UUID due to user must format the value 
> manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3835) Update documentaion for IGFS secondary file system.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3835:
-
Fix Version/s: (was: 1.8)

> Update documentaion for IGFS secondary file system.
> ---
>
> Key: IGNITE-3835
> URL: https://issues.apache.org/jira/browse/IGNITE-3835
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, IGFS
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>
> Now https://apacheignite-fs.readme.io/docs/secondary-file-system page has 
> description of deprecated variant of secondary file system usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3794) Cleanup FormUtils.service.js

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3794:
-
Fix Version/s: (was: 1.8)

> Cleanup FormUtils.service.js
> 
>
> Key: IGNITE-3794
> URL: https://issues.apache.org/jira/browse/IGNITE-3794
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>
> Refactor to class how in ErrorPopover.service



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2547) Expand node with metadata for current selected cache

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2547:
-
Fix Version/s: (was: 1.8)

> Expand node with metadata for current selected cache
> 
>
> Key: IGNITE-2547
> URL: https://issues.apache.org/jira/browse/IGNITE-2547
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> In current implementation we show all caches metadata collapsed, but it make 
> sense to expand node for current selected cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2617) Add spining wheel for long-time operation

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2617:
-
Fix Version/s: (was: 1.8)

> Add spining wheel for long-time operation
> -
>
> Key: IGNITE-2617
> URL: https://issues.apache.org/jira/browse/IGNITE-2617
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>
> For example try to Export All after SCAN of very large table



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3895) Web console: Should split large generated XML and Java files.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3895:
-
Fix Version/s: (was: 1.8)
   2.0

> Web console: Should split large generated XML and Java files.
> -
>
> Key: IGNITE-3895
> URL: https://issues.apache.org/jira/browse/IGNITE-3895
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Vasiliy Sisko
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3930) Web Console: improve generated project usability

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3930:
-
Fix Version/s: (was: 1.8)

> Web Console: improve generated project usability
> 
>
> Key: IGNITE-3930
> URL: https://issues.apache.org/jira/browse/IGNITE-3930
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Current project generated by Web Console is suitable to play with in some IDE.
> It will be very useful if we also generate projects suitable to deploy on 
> server nodes and client nodes by just run {code}mvn clean package{code} and 
> copy resulting jar to target host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4010) Web Console: Implement responsive layout

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4010:
-
Fix Version/s: (was: 1.8)

> Web Console: Implement responsive layout
> 
>
> Key: IGNITE-4010
> URL: https://issues.apache.org/jira/browse/IGNITE-4010
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Andrey Novikov
>Priority: Minor
>
> Add responsive width for body.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4010) Web Console: Implement responsive layout

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4010:
-
Assignee: (was: Maxim Afanasiev)

> Web Console: Implement responsive layout
> 
>
> Key: IGNITE-4010
> URL: https://issues.apache.org/jira/browse/IGNITE-4010
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Andrey Novikov
>Priority: Minor
>
> Add responsive width for body.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3934) Web Console: Capacity planning

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3934:
-
Fix Version/s: (was: 1.8)

> Web Console: Capacity planning
> --
>
> Key: IGNITE-3934
> URL: https://issues.apache.org/jira/browse/IGNITE-3934
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Alexey Kuznetsov
>
> We have a capacity planning page [1] in docs, but it's not very easy to 
> follow this guide when data is loaded from a large database with 100s of 
> tables. How about we add this calculation to the Web Console? I think we can 
> do this during the model import - get the counts of each table and 
> approximate the size of each table's row.
> [1] http://apacheignite.gridgain.org/v1.7/docs/capacity-planning



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3945) Web console: Implement configuration of DeploymentSpi

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3945:
-
Fix Version/s: (was: 1.8)

> Web console: Implement configuration of DeploymentSpi
> -
>
> Key: IGNITE-3945
> URL: https://issues.apache.org/jira/browse/IGNITE-3945
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1081) Create integration for OrientDB

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1081:
-
Fix Version/s: (was: 1.8)
   2.0

> Create integration for OrientDB
> ---
>
> Key: IGNITE-1081
> URL: https://issues.apache.org/jira/browse/IGNITE-1081
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: sprint-7
>Reporter: Alexey Kuznetsov
>Assignee: Gianfranco Murador
>Priority: Minor
>  Labels: newbie
> Fix For: 2.0
>
>
> Create integration for OrientDB
> Create integration for OrientDB https://github.com/orientechnologies/orientdb
> OHazelcastPlugin can be used as start point: 
> https://github.com/orientechnologies/orientdb/blob/master/distributed/src/main/java/com/orientechnologies/orient/server/hazelcast/OHazelcastPlugin.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4068:
-
Fix Version/s: (was: 1.8)

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4064) Web console: Clear filter functionality.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4064:
-
Fix Version/s: (was: 1.8)

> Web console: Clear filter functionality.
> 
>
> Key: IGNITE-4064
> URL: https://issues.apache.org/jira/browse/IGNITE-4064
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>
> # Add "X" button in right side of every non empty filter field to clear 
> filter.
> # Clear filter on press of Esc button. Possible focus independent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4072) Web console: Disable Anotation variant of "Query metadata" when POJO is disabled.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4072:
-
Fix Version/s: (was: 1.8)

> Web console: Disable Anotation variant of "Query metadata" when POJO is 
> disabled.
> -
>
> Key: IGNITE-4072
> URL: https://issues.apache.org/jira/browse/IGNITE-4072
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>
> On model page:
> # Uncheck "Generate POJO classes"
> # Select Anotation variant of "Query metadata" field.
> # Input invalid java class names in "Key type" and "Value type" fields.
> # Switch preview generation to Java.
> Generated code is invalid and should not be possible.
> cache.setIndexedTypes(
> 6adved.class, 
> WRONG_NAME.class
> );



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4081) Web Console: Refactor legacy code

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4081:
-
Fix Version/s: (was: 1.8)

> Web Console: Refactor legacy code
> -
>
> Key: IGNITE-4081
> URL: https://issues.apache.org/jira/browse/IGNITE-4081
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> This is a root ticket for legacy code refactorings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2025) visorcmd doesn't clear local cache on client node

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2025:
-
Fix Version/s: (was: 1.8)

> visorcmd doesn't clear local cache on client node
> -
>
> Key: IGNITE-2025
> URL: https://issues.apache.org/jira/browse/IGNITE-2025
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Pavel Konstantinov
>
> # start server and client nodes with local cache
> # populate local cache on client node
> # execute 'cache -c= -a' 
> {code}
> Nodes for: oh_local(@c11)
> ++
> | Node ID8(@), IP  | CPUs | Heap Used | CPU Load |   Up Time| 
> Size | Hi/Mi/Rd/Wr |
> ++
> | AB439AC6(@n0), 127.0.0.1 | 8| 59.63 %   | 4.77 %   | 00:26:04:528 | 0   
>  | Hi: 0   |
> |  |  |   |  |  | 
>  | Mi: 0   |
> |  |  |   |  |  | 
>  | Rd: 0   |
> |  |  |   |  |  | 
>  | Wr: 0   |
> +--+--+---+--+--+--+-+
> | 5F31343A(@n2), 127.0.0.1 | 8| 84.63 %   | 3.00 %   | 00:17:37:568 | 0   
>  | Hi: 0   |
> |  |  |   |  |  | 
>  | Mi: 0   |
> |  |  |   |  |  | 
>  | Rd: 0   |
> |  |  |   |  |  | 
>  | Wr: 0   |
> +--+--+---+--+--+--+-+
> | 0251B9C4(@n1), 127.0.0.1 | 8| 26.68 %   | 3.60 %   | 00:25:47:708 | 0   
>  | Hi: 27144   |
> |  |  |   |  |  | 
>  | Mi: 18156   |
> |  |  |   |  |  | 
>  | Rd: 45300   |
> |  |  |   |  |  | 
>  | Wr: 186820  |
> ++
> {code}
> # execute 'cache -clear -c=
> {code}
> visor> cache -clear -c=oh_local
> Cleared cache with name: oh_local
> +==+
> |  Node ID8(@)  | Cache Size Before | Cache Size After |
> +==+
> | AB439AC6(@n0) | 0 | 0|
> +--+
> {code}
> # then execute 'cache -c= -a' 
> {code}
> Nodes for: oh_local(@c11)
> ++
> | Node ID8(@), IP  | CPUs | Heap Used | CPU Load |   Up Time| 
> Size | Hi/Mi/Rd/Wr |
> ++
> | AB439AC6(@n0), 127.0.0.1 | 8| 59.63 %   | 4.77 %   | 00:26:04:528 | 0   
>  | Hi: 0   |
> |  |  |   |  |  | 
>  | Mi: 0   |
> |  |  |   |  |  | 
>  | Rd: 0   |
> |  |  |   |  |  | 
>  | Wr: 0   |
> +--+--+---+--+--+--+-+
> | 5F31343A(@n2), 127.0.0.1 | 8| 84.63 %   | 3.00 %   | 00:17:37:568 | 0   
>  | Hi: 0   |
> |  |  |   |  |  | 
>  | Mi: 0   |
> |  |  |   |  |  | 
>  | Rd: 0   |
> |  |  |   |  |  | 
>  | Wr: 0   |
> +--+--+---+--+--+--+-+
> | 0251B9C4(@n1), 127.0.0.1 | 8| 26.68 %   | 3.60 %   | 00:25:47:708 | 0   
>  | Hi: 27144   |
> |  |  |   |  |  | 
>  | Mi: 18156   |
> |  |  |   |  |  | 
>  | Rd: 45300   |
> |  |  |   |  |  | 
>  | Wr: 186820  |
> ++
> {code}
> visorcmd should send 'clear' to all nodes in case of local cache or ask user 
> to point node



--
This message was sent by Atlassian JIRA

[jira] [Closed] (IGNITE-1887) REST-HTTP change queryId generation from sequence to random.

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-1887.
--

> REST-HTTP change queryId generation from sequence to random.
> 
>
> Key: IGNITE-1887
> URL: https://issues.apache.org/jira/browse/IGNITE-1887
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Novikov
>Priority: Minor
> Fix For: 1.8
>
>
> First problem:
>  1. client1 execute query and get queryId = 1.
>  2. node where query was executed is restarted (queryId generator
> initialized to zero).
>  3. client2 execute some query and also get queryId=1.
>  4. client1 fetch next page for queryId=1 and GETS results of client2.
> Second problem:
>  As queryId is generated sequentially it is very easy to brute force and
> some client could get data of other clients too easy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1099) Need to cleanup git

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1099:
-
Fix Version/s: (was: 1.8)

> Need to cleanup git
> ---
>
> Key: IGNITE-1099
> URL: https://issues.apache.org/jira/browse/IGNITE-1099
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Alexey Kuznetsov
>
> * Need to resurrect tool (formerly named JiraBranchesToHtml) that shows up 
> branches for closed tickets in JIRA
> * Need to go through the branches and determine what branches are useless:
> ** ignite-sprint-*
> ** branches with no activity for recent months



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-768) Failed to start LOCAL cache on part of the grid

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-768:

Fix Version/s: (was: 1.8)

> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
> Attachments: 
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException: 
> Failed to start cache (a cache with the same name is already started): 
> local-nid
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
>   at 
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-731) ClusterGroup.forRandom() should return empty projection in case of empty source projection

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-731:

Fix Version/s: (was: 1.8)

> ClusterGroup.forRandom() should return empty projection in case of empty 
> source projection
> --
>
> Key: IGNITE-731
> URL: https://issues.apache.org/jira/browse/IGNITE-731
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: sprint-3
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> I found that ClusterGroup.forRandom() is inconsistent for me.
> If I try to take forRandom() on empty cluster group
>  it throws "java.lang.IllegalArgumentException: n must be positive" 
> I think forRandom() should return empty cluster group in order to not check 
> if source projection is empty.
> Or at least throws exception with meaningful text.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-184) visorcmd: improve auto-calculation of width of table columns

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-184:

Fix Version/s: (was: 1.8)

> visorcmd: improve auto-calculation of width of table columns
> 
>
> Key: IGNITE-184
> URL: https://issues.apache.org/jira/browse/IGNITE-184
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-1
> Environment: I suggest to use following logic:
> if parameter value is a set of values separated by space then print this 
> separated values from new line
> Use terminal width to determine table columns maximum width
>Reporter: Alexey Kuznetsov
> Attachments: gg-8723.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-220) Continuations do not work as expected for anonymous IgniteCallable

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-220:

Fix Version/s: (was: 1.8)

> Continuations do not work as expected for anonymous IgniteCallable
> --
>
> Key: IGNITE-220
> URL: https://issues.apache.org/jira/browse/IGNITE-220
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
> Attachments: ContinuationTest.java
>
>
> Please find test in attached file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-376) Scala examples should be runnable form sbt.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-376:

Fix Version/s: (was: 1.8)

> Scala examples should be runnable form sbt.
> ---
>
> Key: IGNITE-376
> URL: https://issues.apache.org/jira/browse/IGNITE-376
> Project: Ignite
>  Issue Type: Task
>  Components: build
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>
> From dev-list:
> I downloaded the latest version of apache-ignite and am trying to run the
> scala examples in the examples/ subdir.
> However, I am not sure what needs to be done for them to be run. I created
> an sbt project, included the dependencies on the correct libraries like
> ignite-core, ignite-scalar, ignite-examples, however this line keeps
> failing from an example such as the Pi calculation:
> import org.apache.ignite.scalar.scalar
> If I look at the scala docs there is no scalar.scalar.
> Are the examples simply too stale?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2047) Improvements for Ignite Web Console for next releases

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2047:
-
Fix Version/s: (was: 1.8)

> Improvements for Ignite Web Console for next releases
> -
>
> Key: IGNITE-2047
> URL: https://issues.apache.org/jira/browse/IGNITE-2047
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Konstantinov
>
> This is a parent ticket for future improvements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2049) Add to GridProductVersionSelfTest new tests for new naming strategy

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2049:
-
Fix Version/s: (was: 1.8)

> Add to GridProductVersionSelfTest new tests for new naming strategy
> ---
>
> Key: IGNITE-2049
> URL: https://issues.apache.org/jira/browse/IGNITE-2049
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Affects Versions: 1.5.0.final
>Reporter: Alexey Kuznetsov
>  Labels: newbie
>
> See 
> http://apache-ignite-developers.2346864.n4.nabble.com/EA-versioning-td5381.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2073) GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2073:
-
Fix Version/s: (was: 1.8)

> GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter
> --
>
> Key: IGNITE-2073
> URL: https://issues.apache.org/jira/browse/IGNITE-2073
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Pavel Konstantinov
>
> I have such cache configuration
> {code}
> 
> 
> 
> 
> 
> 
> java.util.UUID
> org.my.tester.sql.Car
> 
> 
> 
> {code}
> When I'm doing SQL "select * from Car" via REST I'm got:
> {code}
> Error: 
> org.apache.ignite.internal.processors.cache.local.atomic.GridLocalAtomicCache 
> cannot be cast to 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4091) Refactor direct usage of Angular API

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4091:
-
Fix Version/s: (was: 1.8)
   2.0

> Refactor direct usage of Angular API
> 
>
> Key: IGNITE-4091
> URL: https://issues.apache.org/jira/browse/IGNITE-4091
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Alexey Kuznetsov
> Fix For: 2.0
>
>
> It is not recommended to use Angular API in user code (because it may be 
> changed by Angular developers).
> All usage of angular.XXX should be replaced with appropriate functions from 
> lodash library.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4083) Refactor services to classes

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4083:
-
Fix Version/s: (was: 1.8)
   2.0

> Refactor services to classes
> 
>
> Key: IGNITE-4083
> URL: https://issues.apache.org/jira/browse/IGNITE-4083
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Alexey Kuznetsov
> Fix For: 2.0
>
>
> Refactor services from functions to classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4166) Web console: Add missed properties of POJO store configuration.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4166:
-
Fix Version/s: (was: 1.8)
   2.0

> Web console: Add missed properties of POJO store configuration.
> ---
>
> Key: IGNITE-4166
> URL: https://issues.apache.org/jira/browse/IGNITE-4166
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
> Fix For: 2.0
>
>
> Now configured only Dialect property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2210) Cannot query annotated methods when BinaryMarshaller is set.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2210:

Fix Version/s: (was: 1.8)
   2.0

> Cannot query annotated methods when BinaryMarshaller is set.
> 
>
> Key: IGNITE-2210
> URL: https://issues.apache.org/jira/browse/IGNITE-2210
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>
> Because it is impossible to call method from object in binary form. Several 
> solutions could be applied here:
> 1) Throw exception when method annotation is found and BinaryMarshaller is 
> set.
> 2) Or call this method and record it as a field to the object.
> Sample test: 
> IgniteCacheAbstractFieldsQuerySelfTest.testMethodAnnotationWithoutGet



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2845) Get operation might ignore entry update from EntryProcessor.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2845:

Fix Version/s: (was: 1.8)
   2.0

> Get operation might ignore entry update from EntryProcessor.
> 
>
> Key: IGNITE-2845
> URL: https://issues.apache.org/jira/browse/IGNITE-2845
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>
> Originally issue was observed during work with IGFS. Steps to reproduce:
> 1) Start REPLICATE cache.
> 2) Start PESSIMISITC/REPEATABLE_READ transaction.
> 3) Invoke EntryProcessor on non-existent key and call 
> "MutableEntry.setValue()" inside it.
> 4) Call {{IgniteCache.get()}} on this value. It will return {{null}}, while 
> normally it should return value set inside EntryProcessor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2933) Deprecate GridFunc class.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2933:

Fix Version/s: (was: 1.8)
   2.9

> Deprecate GridFunc class.
> -
>
> Key: IGNITE-2933
> URL: https://issues.apache.org/jira/browse/IGNITE-2933
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2334) Consider getting rid of XXX8 data structures.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2334:

Fix Version/s: (was: 1.8)
   2.0

> Consider getting rid of XXX8 data structures.
> -
>
> Key: IGNITE-2334
> URL: https://issues.apache.org/jira/browse/IGNITE-2334
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> Current state of Java 8 data structures differs from our "jsr166" data 
> structures. 
> One noticeable change is how size is handled inside ConcurrentHashMap. 
> Instead of using LongAdder, it has some inlined version of adder which is 
> more suitable for map operations. 
> But our outdated implementation ConcurrentHashMap8 still uses LongAdder8 and 
> it is seen as a hotspot in profiler.
> We should evaluate whether it still makes sense to keep our versions of 
> concurrent structures.
> 1) Quickly replace all *8* data structures with their normal counterparts.
> 2) Run benchmarks with Java7 and Java8. 
> 3) Decide whether change is needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2779:

Fix Version/s: (was: 1.8)
   2.0

> BinaryMarshaller caches must be cleaned during client reconnect.
> 
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
>  Issue Type: Task
>  Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: community, important
> Fix For: 2.0
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here: 
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all 
> server nodes were down), it doesn't re-send binary metadata to topology. As a 
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1650) Add ability to specify thread pool for IgniteFuture listen/chain methods.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1650:

Fix Version/s: (was: 1.8)
   2.0

> Add ability to specify thread pool for IgniteFuture listen/chain methods.
> -
>
> Key: IGNITE-1650
> URL: https://issues.apache.org/jira/browse/IGNITE-1650
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 2.0
>
>
> Closures passed to IgniteFuture listen() and chain() methods are executed 
> either in the same thread if future is completed, or in a completion thread 
> (usually this is a thread from one of Ignite pools).
> This enforces restrictions on what user can do in closures. He cannot use 
> call operations, he cannot call any Ignite operations. Otherwise deadlocks or 
> starvation could occur.
> To fix that we should allow user to pass optional thread pool where passed 
> closure should be executed. This already done in Java 8 CompletableFuture. We 
> should do almost the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2216:

Fix Version/s: (was: 1.8)
   2.0

> Duplicate field names with aliases do not work in queries.
> --
>
> Key: IGNITE-2216
> URL: https://issues.apache.org/jira/browse/IGNITE-2216
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2671) Node cannot join topology when cache lock is held.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2671:

Fix Version/s: (was: 1.8)
   2.0

> Node cannot join topology when cache lock is held.
> --
>
> Key: IGNITE-2671
> URL: https://issues.apache.org/jira/browse/IGNITE-2671
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: community
> Fix For: 2.0
>
>
> The problem is originally reported by Mario: 
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-td3031.html
> *Description*
> When a lock is held on a cache key, another node cannot join topology. It 
> hangs somewhere on partition exchange future.
> *Steps to reproduce*
> Run the following code and observe that ">>> STARTED 2" is never printed 
> because we cannot leave Ignition.start() method.
> {code}
> public static void main(String[] args) {
> // Start the first node.
> Ignite ignite = Ignition.start(new 
> IgniteConfiguration().setGridName("1"));
> System.out.println(">>> STARTED 1");
> // Create cache and obtain a lock on it.
> CacheConfiguration ccfg =
> new CacheConfiguration String>().setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ignite.getOrCreateCache(ccfg).lock("key").lock();
> System.out.println(">>> LOCKED");
> Ignition.start(new IgniteConfiguration().setGridName("2"));
> System.out.println(">>> STARTED 2");
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2933) Deprecate GridFunc class.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2933:

Fix Version/s: (was: 2.9)
   2.0

> Deprecate GridFunc class.
> -
>
> Key: IGNITE-2933
> URL: https://issues.apache.org/jira/browse/IGNITE-2933
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3159) WebSession: Incorrect handling of HttpServletRequest.getRequestedSessionId.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3159:

Fix Version/s: (was: 1.8)
   2.0

> WebSession: Incorrect handling of HttpServletRequest.getRequestedSessionId.
> ---
>
> Key: IGNITE-3159
> URL: https://issues.apache.org/jira/browse/IGNITE-3159
> Project: Ignite
>  Issue Type: Bug
>  Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> {{WebSessionFilter}} use HttpServletRequest.getRequestedSessionId() method to 
> get session ID.
> However, specification says that this method might return ID which is 
> different from ID of currently active session. E.g. when request is performed 
> with ID of already invalidated session. But we never account for this and 
> pass this session ID to our session.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3667) IGFS: Local secondary: Ensure that user context is propagated properly to underlying FS operation.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3667:

Fix Version/s: (was: 1.8)
   2.0

> IGFS: Local secondary: Ensure that user context is propagated properly to 
> underlying FS operation.
> --
>
> Key: IGNITE-3667
> URL: https://issues.apache.org/jira/browse/IGNITE-3667
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> If operation was initiated by user X, then it should be processed on behalf 
> of this user, not on behalf of Ignite process owner. 
> See {{IgniteHadoopIgfsSecondaryFileSystem.fileSystemForUser()}} for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2935) GridFunc: Identify safe methods and move them to a new class.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2935:

Fix Version/s: (was: 1.8)
   2.0

> GridFunc: Identify safe methods and move them to a new class.
> -
>
> Key: IGNITE-2935
> URL: https://issues.apache.org/jira/browse/IGNITE-2935
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> 1) Create new class. E.g. {{LangUtils}}.
> 2) Move all non-deprecated methods to it.
> 3) Replace all usages of deprecated methods from "F." to "GridFunc."
> 4) Remove unsafe methods.
> 5) Change {{F}} class to extend {{LangUtils}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3080) Improve Spark documentation for CDH deployment

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3080:

Fix Version/s: (was: 1.8)
   2.0

> Improve Spark documentation for CDH deployment
> --
>
> Key: IGNITE-3080
> URL: https://issues.apache.org/jira/browse/IGNITE-3080
> Project: Ignite
>  Issue Type: Improvement
>  Components: Ignite RDD
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>  Labels: bigdata
> Fix For: 2.0
>
>
> Users might experience classpath issues when running Spark on CDH with YARN. 
> The solution is to add Ignite JARs to YARN classpath through CDH console. 
> Originally explained by Michael Dolgonos here: 
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Installation-with-Spark-under-CDH-tp4457p4624.html
>  
> {quote}
> Cloudera Manager -> YARN (MR2 Included) -> Configuration -> Service Wide ->
> Advanced -> Spark Client Advanced Configuration Snippet (Safety Valve) for
> spark-conf/spark-defaults.conf
> Added etc/ignite-fabric-1.5.0/libs/* to already present
> spark.executor.extraClassPath=/opt/cloudera/parcels/CDH-5.5.2-1.cdh5.5.2.p0.4/jars/htrace-core-3.2.0-incubating.jar.
> The combined line looks like this:
> spark.executor.extraClassPath=/opt/cloudera/parcels/CDH-5.5.2-1.cdh5.5.2.p0.4/jars/htrace-core-3.2.0-incubating.jar:/etc/ignite-fabric-1.5.0/libs/*{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-19) Race condition when offheaped value is being promoted to swap.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-19:
--
Fix Version/s: (was: 1.8)
   2.0

> Race condition when offheaped value is being promoted to swap.
> --
>
> Key: IGNITE-19
> URL: https://issues.apache.org/jira/browse/IGNITE-19
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>
> Eviction from offheap to swap is done using listener on GridUnsafeMap. 
> Notification of this listener happens when value is already deleted from 
> offheap and lock is released (GridUnsafeMap line 860). So "get" operation on 
> cache can miss the value while it is in between.
> Need to:
> 1) Review this code piece;
> 2) Create a test reproducing the issue;
> 3) Fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3084) Investigate how Ignite can support Spark DataFrame

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3084:

Fix Version/s: (was: 1.8)
   2.0

> Investigate how Ignite can support Spark DataFrame
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: Task
>  Components: Ignite RDD
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
>  Labels: bigdata
> Fix For: 2.0
>
>
> We see increasing demand on nice DataFrame support for our Spark integration. 
> Need to investigate how could we do that.
> Looks like we can investigate how MemSQL do that and take it as a starting 
> point.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2826) .NET: Write DataContract types as binary

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2826:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Write DataContract types as binary
> 
>
> Key: IGNITE-2826
> URL: https://issues.apache.org/jira/browse/IGNITE-2826
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Types marked with [DataContract] attribute should be written in binary 
> format, respecting [DataMember] and other related attributes, so that 
> existing user types can be used in Ignite without any changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2827) .NET: Write XmlSerializer types as binary

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2827:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Write XmlSerializer types as binary
> -
>
> Key: IGNITE-2827
> URL: https://issues.apache.org/jira/browse/IGNITE-2827
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Types intended to be serialized with XmlSerializer can be identified by 
> [XmlRoot] attribute, or one of the [XmlElement], [XmlAttribute], etc 
> attributes on type members.
> We should write such types using Ignite binary format, and respect attributes 
> where applicable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3006) .NET: ContinuousQuery.FilterFactory

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3006:

Fix Version/s: (was: 1.8)
   2.0

> .NET: ContinuousQuery.FilterFactory
> ---
>
> Key: IGNITE-3006
> URL: https://issues.apache.org/jira/browse/IGNITE-3006
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> To conform to Java APIs:
> * Add ContinuousQuery.FilterFactory
> * Deprecate  ContinuousQuery.Filter
> Make sure that resource injection works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2626) Binary marshaller: sort fields alphabetically

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2626:

Fix Version/s: (was: 1.8)
   2.0

> Binary marshaller: sort fields alphabetically
> -
>
> Key: IGNITE-2626
> URL: https://issues.apache.org/jira/browse/IGNITE-2626
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> Currently we write object fields in the order they come from reflection.
> 1) There is no guarantee that this order is consistent across multiple calls
> 2) Platforms may have corresponding objects with different field order
> => There are situations when write and read field order is different, which 
> hurts performance.
> Sorting fields alphabetically in Java and platforms will ensure the same 
> ordering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2890) .NET: Add CacheConfiguration.NodeFilter

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2890:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Add CacheConfiguration.NodeFilter
> ---
>
> Key: IGNITE-2890
> URL: https://issues.apache.org/jira/browse/IGNITE-2890
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> See ServiceConfiguration.NodeFilter
> * Caches start earlier than platform => need to pass pointer for static 
> CacheConfigurations
> * For dynamic cache start, no need for pointers



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3111) .NET: Configure SSL without Spring

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3111:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Configure SSL without Spring
> --
>
> Key: IGNITE-3111
> URL: https://issues.apache.org/jira/browse/IGNITE-3111
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net, roadmap
> Fix For: 2.0
>
>
> User should be able to configure SLL in .NET terms without Spring and Java 
> KeyStore.
> See https://apacheignite.readme.io/docs/ssltls.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3088) .NET: Support POCO proxy serialization

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3088:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Support POCO proxy serialization
> --
>
> Key: IGNITE-3088
> URL: https://issues.apache.org/jira/browse/IGNITE-3088
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> WCF provides a way to serialize POCO proxies: 
> https://msdn.microsoft.com/en-us/library/ee705457(v=vs.100).aspx
> We should come up with a way to do this.
> To reproduce: 
> * Create a database with 2 tables and a foreign key; populate some rows
> * Create a new EF6 project from that database
> * Retrieve one of the entities
> * Attempt to put it into cache



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3025) CPP: C++ client node can not access the cache for which PlatformDotNetCacheStoreFactory is used.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3025:

Fix Version/s: (was: 1.8)
   2.0

> CPP: C++ client node can not access the cache for which 
> PlatformDotNetCacheStoreFactory is used.
> 
>
> Key: IGNITE-3025
> URL: https://issues.apache.org/jira/browse/IGNITE-3025
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> If there is .NET node with {{PlatformDotNetCacheStoreFactory}} configured for 
> some cache then this cache can not be accessed by the C++ client node.
> Following error observed on the attempt to access the cache:
> {noformat}
> [GridDhtPartitionsExchangeFuture] Failed to reinitialize local partitions 
> (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], nodeId=2bf10735, evt=DISCOVERY_CUSTOM_EVT]
> PlatformNoCallbackException []
> at 
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.cacheStoreCreate(Native
>  Method)
> at 
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.cacheStoreCreate(PlatformCallbackGateway.java:63)
> at 
> org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetCacheStore.initialize(PlatformDotNetCacheStore.java:338)
> at 
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.registerStore0(PlatformProcessorImpl.java:347)
> at 
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.registerStore(PlatformProcessorImpl.java:317)
> at 
> org.apache.ignite.internal.processors.cache.store.CacheOsStoreManager.start0(CacheOsStoreManager.java:60)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.start(GridCacheManagerAdapter.java:50)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1051)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1648)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1563)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:956)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:523)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4070) .NET: Introduce transformers to SCAN queries

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4070:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Introduce transformers to SCAN queries
> 
>
> Key: IGNITE-4070
> URL: https://issues.apache.org/jira/browse/IGNITE-4070
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Same thing in .NET as IGNITE-2546. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3102) .NET: Call user-defined constructor for IBinarizable objects

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3102:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Call user-defined constructor for IBinarizable objects
> 
>
> Key: IGNITE-3102
> URL: https://issues.apache.org/jira/browse/IGNITE-3102
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Currently we create user objects with 
> FormatterServices.GetUninitializedObject and then call user-defined 
> IBinarizable.ReadBinary method.
> This is not convenient both for us and the user:
> * FormatterServices.GetUninitializedObject is not a clean way of constructing 
> objects
> * User-defined constructor does not get called
> * User types can't have readonly fields
> For example, ISerializable mechanism does not have Read method; it calls 
> user-defined constructor instead. We should provide similar mechanism.
> * To maintain compatibility, we may have to introduce a new interface with a 
> single Write method, and call user-defined ctor on read.
> * Another option is to introduce a [BinarizableInit] attribute. User can 
> place it on a constructor, and Ignite will call it, injecting Reader and 
> Ignite instances to parameters (if there are any).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-481) Add tests for Metrics to the file system tests infrastructure

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-481:
---
Fix Version/s: (was: 1.8)
   2.0

> Add tests for Metrics to the file system tests infrastructure
> -
>
> Key: IGNITE-481
> URL: https://issues.apache.org/jira/browse/IGNITE-481
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.6
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
>Priority: Minor
> Fix For: 2.0
>
>
> Need to add tests for org.apache.ignite.igfs.IgfsMetrics to the filesystem 
> tests.
> See org.apache.ignite.IgniteFileSystem#metrics , 
> org.apache.ignite.IgniteFileSystem#resetMetrics .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2701) Binary mode in Data Structures

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2701:

Fix Version/s: (was: 1.8)
   2.0

> Binary mode in Data Structures
> --
>
> Key: IGNITE-2701
> URL: https://issues.apache.org/jira/browse/IGNITE-2701
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.0
>
>
> Add binary mode (withKeepBinary) to Data Structures (Queue, AtomicReference).
> This will allow retrieving values in binary format when needed or when class 
> is not available, and will allow implementing these structures in other 
> platforms (.NET, C++).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2398) .NET: Change default mapper behavior.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2398:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Change default mapper behavior.
> -
>
> Key: IGNITE-2398
> URL: https://issues.apache.org/jira/browse/IGNITE-2398
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net, important
> Fix For: 2.0
>
>
> We need to mirror changes implemented in IGNITE-2191:
> 1) Default mapper must use full class name (i.e. with package)
> 2) Provide additional mapper implementation which will use simple names.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2580) Investigate HashMap.Node[] allocations from GridDhtTxPrepareFuture.readyLocks(Iterable)

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2580:

Fix Version/s: (was: 1.8)
   2.0

> Investigate HashMap.Node[] allocations from 
> GridDhtTxPrepareFuture.readyLocks(Iterable)
> ---
>
> Key: IGNITE-2580
> URL: https://issues.apache.org/jira/browse/IGNITE-2580
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>  Labels: performance
> Fix For: 2.0
>
>
> *Problem*
> GridDhtTxPrepareFuture is initialized with empty HashSet by default. When 
> single lock is ready HashSet.add() is called causing immediate expansion of 
> underlying HashMap table.
> *Solution*
> Do we really need fully-fledged hash set immediately? Probably we can 
> optimize for single-lock case so that HashSet is not needed at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)