[jira] [Resolved] (IGNITE-1634) We should generate POJO classes in Client configuration too

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-1634.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Added showing op POJO classes in client section.

> We should generate POJO classes in Client configuration too
> ---
>
> Key: IGNITE-1634
> URL: https://issues.apache.org/jira/browse/IGNITE-1634
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Currently we do not generate POJO for Client.



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

[jira] [Commented] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-1555:
-

Guys,

My main concern here is that the name should be easy to understand for end 
users. 
"ignite-hadoop" and "Ignite Hadoop Accelerator" are good names because users 
understand what they have in hands right away. 
"ignite-accelerator" raises questions what exactly we accelerate.
"ignite-integration" is a better option, but it is inconsistent with the rest 
available Ignite integrations. Users simply would not understand why Hadoop and 
Spark are inside "integration" build, while Hibernate, Mesos, Kafka and a dozen 
of others are in "fabric" build.

Can we leave the name "ignite-hadoop" as is and simply include Spark dependency 
into it? It could be a good compromise for both Ignite and BigTop products for 
now.

> Combine ignite-hadoop and ignite-spark into signle assembly for downstream 
> consumption.
> ---
>
> Key: IGNITE-1555
> URL: https://issues.apache.org/jira/browse/IGNITE-1555
> Project: Ignite
>  Issue Type: New Feature
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 1.5
>
> Attachments: IGNITE-1555.patch, IGNITE-1555.patch, IGNITE-1555.patch
>
>
> Let's combine all nice things that Ignite provides for Hadoop and Spark into 
> single assembly called ignite-accelerator. This will be advantageous for 
> downstream integrators like Bigtop, where all bits can be packaged together, 
> tested, and deployed with proper configurations and permissions to avoid 
> interoperability issues. A typical is when spark-shell starts an Ignite node 
> which crashes because user 'spark' isn't allowed to write into Ignite's 
> work-dir, etc.



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

[jira] [Assigned] (IGNITE-1168) REST API: type metadata for cache

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-1168:


Assignee: Andrey Novikov  (was: Semen Boikov)

Looks good.

> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 1.5
>
> Attachments: IGNITE-1168.patch, master_a1e5cc5_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



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

[jira] [Resolved] (IGNITE-1596) Web console agent improvements

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-1596.

Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Andrey Novikov)

Fixed all issue from description.

> Web console agent improvements
> --
>
> Key: IGNITE-1596
> URL: https://issues.apache.org/jira/browse/IGNITE-1596
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> * Help message should state if the parameter is optional. Ideally default 
> values should be provided on the next line.
> * Default value for config-path should be provided. Text should say: Path to 
> agent property file
> * When started without parameters, web agent should start with defaults 
> instead of printing help message.
> * When started (with or without parameters), agent should print out values 
> for all the configuration settings.
> * We should have a suggestion saying: To start web-agent in test-drive mode, 
> pass "-tm" and "-ts" parameters
> * Before prompting for token, agent should say: 
> Security token is required to establish connection to the web console. 
> It is available on the Profile page: https://URL
> Enter security token:



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

[jira] [Resolved] (IGNITE-1594) Home page for web console

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-1594.
--
Resolution: Fixed

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Alexey Kuznetsov
> Fix For: 1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



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

[jira] [Commented] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1572:
-

1) I have fixed TestPortableObjectInTask by adding a wrapper in the test 
itself. This use is very unlikely, so we can tell users to create their own 
wrapper (which is trivial).
2) .

> .Net: Check if we can get rid of "WritePortableOrSerializable" method.
> --
>
> Key: IGNITE-1572
> URL: https://issues.apache.org/jira/browse/IGNITE-1572
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: 1.5
>
>
> We have lots of places where "WritePortableOrSerializable" routine is 
> invoked. It is not clear why do we need it provided that we already handle 
> [Serializable] classes properly. 
> Looks like we are able to get rid of it safely, aren't we? Need to 
> double-check.



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

[jira] [Updated] (IGNITE-1168) REST API: type metadata for cache

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-1168:
---
Assignee: Sergey Kozlov  (was: Andrey Novikov)

> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
> Attachments: IGNITE-1168.patch, master_a1e5cc5_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



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

[jira] [Updated] (IGNITE-1649) TcpDiscoverySpi configuraiton in cluster configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-1649:
--
Description: 
# Add configuration of TcpDiscoverySpi on cluster configuration page.
# Add configuration of TcpCommunicationSpi on cluster configuration page.

  was:Add configuration of TcpDiscoverySpi on cluster configuration page.


> TcpDiscoverySpi configuraiton in cluster configuration
> --
>
> Key: IGNITE-1649
> URL: https://issues.apache.org/jira/browse/IGNITE-1649
> Project: Ignite
>  Issue Type: Sub-task
>  Components: website
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
>
> # Add configuration of TcpDiscoverySpi on cluster configuration page.
> # Add configuration of TcpCommunicationSpi on cluster configuration page.



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

[jira] [Commented] (IGNITE-1617) CPP: review string usage in public API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1617:


Github user isapego closed the pull request at:

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


> CPP: review string usage in public API 
> ---
>
> Key: IGNITE-1617
> URL: https://issues.apache.org/jira/browse/IGNITE-1617
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Currently there is std::string type used in some parts of public API while 
> const char* used in some other parts. Need to review API and suggest solution 
> for the consistent string policy.



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

[jira] [Commented] (IGNITE-1649) TcpDiscoverySpi configuraiton in cluster configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-1649:
---

# Implemented configuration of TcpDiscoverySpi.

> TcpDiscoverySpi configuraiton in cluster configuration
> --
>
> Key: IGNITE-1649
> URL: https://issues.apache.org/jira/browse/IGNITE-1649
> Project: Ignite
>  Issue Type: Sub-task
>  Components: website
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
>
> # Add configuration of TcpDiscoverySpi on cluster configuration page.
> # Add configuration of TcpCommunicationSpi on cluster configuration page.



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

[jira] [Updated] (IGNITE-1652) .Net: Rework async APIs (remove WithAsync/GetFuture)

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1652:

Description: 
{code}
cache.WithAsync().Get();
var future = cache.GetFuture();
{code}

should become

{code}
var future = cache.GetAsync();
{code}

See if we can make ToTask() more efficient, or even get rid of Futures 
completely in favor of tasks, preserving performance.

First step is .Net-only (remove GetFuture from public API, call it inside 
*Async methods). This requires 2 JNI calls.

Later we should look into making it a single JNI call.


  was:
{code}
cache.WithAsync().Get();
var future = cache.GetFuture();
{code}

should become

{code}
var future = cache.GetAsync();
{code}

First step is .Net-only (remove GetFuture from public API, call it inside 
*Async methods). This requires 2 JNI calls.

Later we should look into making it a single JNI call.



> .Net: Rework async APIs (remove WithAsync/GetFuture)
> 
>
> Key: IGNITE-1652
> URL: https://issues.apache.org/jira/browse/IGNITE-1652
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> {code}
> cache.WithAsync().Get();
> var future = cache.GetFuture();
> {code}
> should become
> {code}
> var future = cache.GetAsync();
> {code}
> See if we can make ToTask() more efficient, or even get rid of Futures 
> completely in favor of tasks, preserving performance.
> First step is .Net-only (remove GetFuture from public API, call it inside 
> *Async methods). This requires 2 JNI calls.
> Later we should look into making it a single JNI call.



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

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

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1650:
---

 Summary: 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
Priority: Critical
 Fix For: 1.6


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] [Created] (IGNITE-1651) Add version to portable object header.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1651:
---

 Summary: Add version to portable object header.
 Key: IGNITE-1651
 URL: https://issues.apache.org/jira/browse/IGNITE-1651
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 1.5






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

[jira] [Created] (IGNITE-1652) .Net: Rework async APIs (remove WithAsync/GetFuture)

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1652:
---

 Summary: .Net: Rework async APIs (remove WithAsync/GetFuture)
 Key: IGNITE-1652
 URL: https://issues.apache.org/jira/browse/IGNITE-1652
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: 1.5
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: 1.5


{code}
cache.WithAsync().Get();
var result = cache.GetFuture();
{code}

should become

{code}
var result = cache.GetAsync();
{code}

First step is .Net-only (remove GetFuture from public API, call it inside 
*Async methods). This requires 2 JNI calls.

Later we should look into making it a single JNI call.




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

[jira] [Updated] (IGNITE-1652) .Net: Rework async APIs (remove WithAsync/GetFuture)

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1652:

Description: 
{code}
cache.WithAsync().Get();
var future = cache.GetFuture();
{code}

should become

{code}
var future = cache.GetAsync();
{code}

First step is .Net-only (remove GetFuture from public API, call it inside 
*Async methods). This requires 2 JNI calls.

Later we should look into making it a single JNI call.


  was:
{code}
cache.WithAsync().Get();
var result = cache.GetFuture();
{code}

should become

{code}
var result = cache.GetAsync();
{code}

First step is .Net-only (remove GetFuture from public API, call it inside 
*Async methods). This requires 2 JNI calls.

Later we should look into making it a single JNI call.



> .Net: Rework async APIs (remove WithAsync/GetFuture)
> 
>
> Key: IGNITE-1652
> URL: https://issues.apache.org/jira/browse/IGNITE-1652
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> {code}
> cache.WithAsync().Get();
> var future = cache.GetFuture();
> {code}
> should become
> {code}
> var future = cache.GetAsync();
> {code}
> First step is .Net-only (remove GetFuture from public API, call it inside 
> *Async methods). This requires 2 JNI calls.
> Later we should look into making it a single JNI call.



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

[jira] [Commented] (IGNITE-1645) .Net: Throw exception on null flag in PortableReader when reading non-nullable value types

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1645:
-

* exceptions added in ReaderImpl and Future.OnNullvalue
* IgniteNullable<> added to handle nulls in Try* methods

> .Net: Throw exception on null flag in PortableReader when reading 
> non-nullable value types
> --
>
> Key: IGNITE-1645
> URL: https://issues.apache.org/jira/browse/IGNITE-1645
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Currently we always return default(T) when deserializing null value. So for 
> value types there is no way  for the user to discern a missing cache key from 
> a cache key with default value.
> * throw exceptions when there is Null in stream and we are trying to read a 
> value type
> * update Cache API with Try* methods



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

[jira] [Updated] (IGNITE-1656) Get rid of md5 and sha1 in favor os sha512

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-1656:
--
Summary: Get rid of md5 and sha1 in favor os sha512  (was: Get rid of md5 
and sha1)

> Get rid of md5 and sha1 in favor os sha512
> --
>
> Key: IGNITE-1656
> URL: https://issues.apache.org/jira/browse/IGNITE-1656
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
> Fix For: 1.5
>
>
> Description of the problem wrt sha1 is there:   
> https://sites.google.com/site/itstheshappening/ .



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

[jira] [Comment Edited] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

[Denis Magda (JIRA)]

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

Denis Magda edited comment on IGNITE-1272 at 10/12/15 3:31 PM:
---

Fixed and reworked the rest of the test that are mentioned in this ticket 
except 7 failing tests from newly added Compute Test Suite.

These tests are not critical and should be reviewed and fixed separately.


was (Author: dmagda):
Fixed and reworked the test of the test that are mentioned in this ticket 
except 7 failing tests from newly added Compute Test Suite.

These tests are not critical and should be reviewed and fixed separately.

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
> Attachments: ignite-1272.patch, ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Commented] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1272:
-

Fixed and reworked the test of the test that are mentioned in this ticket 
except 7 failing tests from newly added Compute Test Suite.

These tests are not critical and should be reviewed and fixed separately.

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
> Attachments: ignite-1272.patch, ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Comment Edited] (IGNITE-1590) IGFS: update & create operations should be truly thread-safe.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky edited comment on IGNITE-1590 at 10/12/15 4:09 PM:
---

done all requested corrections, tests are passing locally & on TC.


was (Author: iveselovskiy):
done all requested corrections, tests are passing locally, waiting for the 
results on TC.

> IGFS: update & create operations should be truly thread-safe.
> -
>
> Key: IGNITE-1590
> URL: https://issues.apache.org/jira/browse/IGNITE-1590
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Fix #create() operation & revise #update().
> Currently the tests with many concurrent operations (involving  
> delete/rename/nkdirs/create) reveal concurrency problems -- some tree entries 
> get "lost".



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

[jira] [Created] (IGNITE-1655) Decouple Date and Timestamp types.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1655:
---

 Summary: Decouple Date and Timestamp types.
 Key: IGNITE-1655
 URL: https://issues.apache.org/jira/browse/IGNITE-1655
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


Date and Timestamp types must be decoupled from each other:
1) New type ID must be introduced for Timestamp
2) New read/write methods should be added to portable readers, writers and 
builder.
3) Configuration parameter "isUseTimestamp" should be removed.
4) .Net DateTime type should be re-mapped to Timestamp.



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

[jira] [Comment Edited] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov edited comment on IGNITE-1526 at 10/12/15 12:48 PM:
--

1. I ran two nodes: 
 under Oracle JDK7: bin\ignite.bat examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false
 under Oracle JDK8:  bin\ignite.bat examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false
2. Build and compile examples in IDEA under IBM JDK7
3. Run EventsExample and get following on nodes:
{noformat}
[15:28:11,524][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed to 
unmarshal discovery custom message.
class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
with given class loader: sun.misc.Launcher$AppClassLoader@18b4aac2
at 
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:105)
at 
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:68)
at 
org.apache.ignite.spi.discovery.tcp.messages.TcpDiscoveryCustomEventMessage.message(TcpDiscoveryCustomEventMessage.java:78)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:4340)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processCustomMessage(ServerImpl.java:4299)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2125)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.io.InvalidClassException: 
org.apache.ignite.internal.util.lang.GridFunc$3; local class incompatible: 
stream classdesc serialVersionUID
 = 1419527628989531832, local class serialVersionUID = 6101914246981105862
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:621)
at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1623)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at 
org.apache.ignite.internal.processors.continuous.StartRequestData.readExternal(StartRequestData.java:258)
at 
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at 
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:102)
... 7 more
[15:28:50,548][INFO][grid-timeout-worker-#33%null%][IgniteKernal]
{noformat}

Similar issues found for MessagingPingPongExample and 
MessagingPingPongListenActor


was (Author: skozlov):
1. I ran two nodes: 
 under Oracle JDK7: bin\ignite.bat examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false
 under Oracle JDK8:  bin\ignite.bat examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false
2. Build and compile examples in IDEA under IBM JDK7
3. Run EventsExample and get following on nodes:
{noformat}
[15:28:11,524][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed to 
unmarshal discovery custom message.
class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
with given class loader: sun.misc.Launcher$AppClassLoader@18b4aac2
at 
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:105)
at 
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:68)
at 
org.apache.ignite.spi.discovery.tcp.messages.TcpDiscoveryCustomEventMessage.message(TcpDiscoveryCustomEventMessage.java:78)
at 

[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-1526:
-

Need to fix problem with Events and move 
{{ignite.marsh.optimized.useDefaultSUID}} property to 
{{IgniteSystemProperties}} class and rename.

> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: 1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some 
> functionality still doesn't work. As an example 
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] 
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing 
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed 
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at 
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.io.InvalidClassException: 
> org.apache.ignite.internal.util.lang.G
> ridFunc$38; local class incompatible: stream classdesc serialVersionUID = 
> -55433
> 49853748590486, local class serialVersionUID = -5664060422647374863
> at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
> at 
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:162
> 2)
> at 
> 

[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov commented on IGNITE-1526:
---

A bit strange case
1. Run 1 node under Oracle JDK7 (bin\ignite.bat 
examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false)
2. Run following examples successively: ComputeReducerExample, 
ComputeRunnableExample, ComputeTaskMapExample, ComputeTaskSplitExample and then 
got following exception:
{noformat}
[16:36:11,921][ERROR][tcp-disco-sock-reader-#10%null][TcpDiscoverySpi] Failed 
to read message [sock=Socket[addr=/0:0:0:0:0:0:0:1,port=63271,localport=47501], 
locNodeId=df1b6d29-292a-4c98-9da0-5509d013e364, 
rmtNodeId=5eb72def-71d4-489d-ac70-0a04bb30f2f1]
class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
with given class loader: sun.misc.Launcher$AppClassLoader@ef968d1d
at 
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:105)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:4785)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.io.StreamCorruptedException: invalid type code: 62
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1461)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:429)
at 
org.apache.ignite.internal.util.IgniteUtils.readMap(IgniteUtils.java:4889)
at 
org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.readExternal(TcpDiscoveryNode.java:559)
at 
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1940)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1899)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1433)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2093)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2018)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1901)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1433)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:429)
at java.util.ArrayDeque.readObject(ArrayDeque.java:876)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at 
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1099)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1996)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1901)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1433)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2093)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2018)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1901)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1433)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:429)
at 
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:102)
... 2 more
{noformat}

> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: 1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some 
> functionality still doesn't work. As an example 
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] 
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
>   at 
> 

[jira] [Comment Edited] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn edited comment on IGNITE-1572 at 10/12/15 11:28 AM:


1) I have fixed TestPortableObjectInTask by adding a wrapper in the test 
itself. This use is very unlikely, so we can tell users to create their own 
wrapper (which is trivial).
2) Actually, this looks like correct behavior. Wrapped serializable type may be 
not present on some remote node, so we return IPortableObject. And if the type 
is present, calling IPortableObject.Deserialize will return correct result.


was (Author: ptupitsyn):
1) I have fixed TestPortableObjectInTask by adding a wrapper in the test 
itself. This use is very unlikely, so we can tell users to create their own 
wrapper (which is trivial).
2) .

> .Net: Check if we can get rid of "WritePortableOrSerializable" method.
> --
>
> Key: IGNITE-1572
> URL: https://issues.apache.org/jira/browse/IGNITE-1572
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: 1.5
>
>
> We have lots of places where "WritePortableOrSerializable" routine is 
> invoked. It is not clear why do we need it provided that we already handle 
> [Serializable] classes properly. 
> Looks like we are able to get rid of it safely, aren't we? Need to 
> double-check.



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

[jira] [Updated] (IGNITE-1655) Decouple Date and Timestamp types.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1655:

Description: 
Date and Timestamp types must be decoupled from each other:
1) New type ID must be introduced for Timestamp
2) New read/write methods should be added to portable readers, writers and 
builder.
3) Configuration parameter "isUseTimestamp" should be removed.
4) .Net DateTime type should be re-mapped to Timestamp.
5) New meta type should be added.

  was:
Date and Timestamp types must be decoupled from each other:
1) New type ID must be introduced for Timestamp
2) New read/write methods should be added to portable readers, writers and 
builder.
3) Configuration parameter "isUseTimestamp" should be removed.
4) .Net DateTime type should be re-mapped to Timestamp.


> Decouple Date and Timestamp types.
> --
>
> Key: IGNITE-1655
> URL: https://issues.apache.org/jira/browse/IGNITE-1655
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> Date and Timestamp types must be decoupled from each other:
> 1) New type ID must be introduced for Timestamp
> 2) New read/write methods should be added to portable readers, writers and 
> builder.
> 3) Configuration parameter "isUseTimestamp" should be removed.
> 4) .Net DateTime type should be re-mapped to Timestamp.
> 5) New meta type should be added.



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

[jira] [Assigned] (IGNITE-1653) Need to remove lgpl-dependent examples from Ignite binaries

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-1653:


Assignee: Anton Vinogradov

> Need to remove lgpl-dependent examples from Ignite binaries
> ---
>
> Key: IGNITE-1653
> URL: https://issues.apache.org/jira/browse/IGNITE-1653
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: Apache-Ignite-1.5.0 build #29
>Reporter: Vasilisa  Sidorova
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Examples project from Ignite binaries couldn't be compiled due to there is 
> lgpl-dependencies.
> Solution: lgpl-dependent examples should be removed from Ignite src and bin



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

[jira] [Comment Edited] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov edited comment on IGNITE-1526 at 10/12/15 1:19 PM:
-

Another failure found:
1. Run 1 node under Oracle JDK7 (bin\ignite.bat 
examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false)
2. Run ComputeFibonacciContinuationExample (IBM JDK7) and got exception:

{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to 
find class with given class loader for unmarshalling (make sure same version of 
all classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@ceddcebd
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:338)
at 
org.apache.ignite.examples.computegrid.ComputeFibonacciContinuationExample.main(ComputeFibonacciContinuationExample.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find class 
with given class loader for unmarshalling (make sure same version of all 
classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@ceddcebd
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:246)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:762)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:809)
Caused by: java.lang.ClassNotFoundException: Optimized stream class checksum 
mismatch (is same version of marshalled class present on all nodes?) 
[expected=-21474, actual=26922, cls=class java.math.BigInteger]
at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.verifyChecksum(OptimizedClassDescriptor.java:824)
at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:806)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:315)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:414)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:240)
... 9 more
{noformat}


was (Author: skozlov):
Another failure found:
1. Run 1 node under Oracle JDK7 (bin\ignite.bat 
examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false)
2. Run ComputeFibonacciContinuationExample and got exception:

{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to 
find class with given class loader for unmarshalling (make sure same version of 
all classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@ceddcebd
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:338)
at 
org.apache.ignite.examples.computegrid.ComputeFibonacciContinuationExample.main(ComputeFibonacciContinuationExample.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find class 
with given 

[jira] [Created] (IGNITE-1654) .Net: Ensure consistent "keepPortable" behavior.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1654:
---

 Summary: .Net: Ensure consistent "keepPortable" behavior.
 Key: IGNITE-1654
 URL: https://issues.apache.org/jira/browse/IGNITE-1654
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


We need to ensure that "keep portable" concept is
a) Consistent;
b) Exists for all logical units where it is necessary.

Lets split "keep portable" behavior in two scenarios:
1) Client mode. This is when client (caller) operates on portable objects. 
Example: ICache.Get(...);
2) Server mode. This is when some server side object (caller) operates on 
portable objects. Example: a remote service which should not deserialize passed 
arguments and operate on portables instead.

Looks like both cases can be handled using the same "keep portable" flag on 
related logical unit.

Logical units affected:
1) Compute - at the very least closures can be executed in this mode;
2) Cache;
3) Data streamer;
4) Data structures: atomic stamped, atmoc reference;
5) Cache events;
6) Messages;
7) Services.

Probably we should introduce a kind of "IKeepPortableEnabled" (or so) 
interface, which will have a method "T WithKeepPortable()". This way users will 
be able to easily understand that "keep portable" semantics is applicable.

Lets split it into several children tickets if necessary.



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

[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov commented on IGNITE-1526:
---

Another failure found:
1. Run 1 node under Oracle JDK7 (bin\ignite.bat 
examples\config\example-ignite.xml -v 
-J-Dignite.marsh.optimized.useDefaultSUID=false)
2. Run ComputeFibonacciContinuationExample and got exception:

{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to 
find class with given class loader for unmarshalling (make sure same version of 
all classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@ceddcebd
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:338)
at 
org.apache.ignite.examples.computegrid.ComputeFibonacciContinuationExample.main(ComputeFibonacciContinuationExample.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find class 
with given class loader for unmarshalling (make sure same version of all 
classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@ceddcebd
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:246)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:762)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:809)
Caused by: java.lang.ClassNotFoundException: Optimized stream class checksum 
mismatch (is same version of marshalled class present on all nodes?) 
[expected=-21474, actual=26922, cls=class java.math.BigInteger]
at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.verifyChecksum(OptimizedClassDescriptor.java:824)
at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:806)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:315)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:414)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:240)
... 9 more
{noformat}

> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: 1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some 
> functionality still doesn't work. As an example 
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] 
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
>   at 
> 

[jira] [Commented] (IGNITE-1656) Get rid of md5 and sha1 in favor of sha512

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-1656:


There's a simple way to deal with it once and for all (this is the HBase, 
Hadoop approach). For all release artifacts you can run something like this:
{{for i in *.tar.gz; do echo $i; gpg --print-mds $i > $i.mds ; done}}
gpg produces a set of checksums, including all available SHA's and some others. 
What's important is that gpg behaves the same way on all platforms, so 
verification format issues will be non-existent.

> Get rid of md5 and sha1 in favor of sha512
> --
>
> Key: IGNITE-1656
> URL: https://issues.apache.org/jira/browse/IGNITE-1656
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
> Fix For: 1.5
>
>
> Description of the problem wrt sha1 is there:   
> https://sites.google.com/site/itstheshappening/ .



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

[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova commented on IGNITE-1526:


The same issue as for Messaging Examples is for ScalarPingPongExample

> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: 1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some 
> functionality still doesn't work. As an example 
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] 
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing 
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed 
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at 
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.io.InvalidClassException: 
> org.apache.ignite.internal.util.lang.G
> ridFunc$38; local class incompatible: stream classdesc serialVersionUID = 
> -55433
> 49853748590486, local class serialVersionUID = -5664060422647374863
> at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
> at 
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:162
> 2)
> at 
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
> at 
> 

[jira] [Commented] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-1555:


Honestly, for last 3 weeks I was trying to see the importance of the name and I 
failed. I personally don't envision anyone using a raw assembly being used to 
install on a cluster for filesystem caching or else. The assembly is going to 
be consumed by downstream projects in an automated fashion. And in such case 
name is  a negligent matter. At any rate, here's the latest version of the 
patch which preserve the name and includes spark integration module into the 
binary assembly. I will commit this by the morrow unless I hear any objections 
on the approach. Thanks!

> Combine ignite-hadoop and ignite-spark into signle assembly for downstream 
> consumption.
> ---
>
> Key: IGNITE-1555
> URL: https://issues.apache.org/jira/browse/IGNITE-1555
> Project: Ignite
>  Issue Type: New Feature
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 1.5
>
> Attachments: IGNITE-1555.patch, IGNITE-1555.patch, IGNITE-1555.patch, 
> IGNITE-1555.patch
>
>
> Let's combine all nice things that Ignite provides for Hadoop and Spark into 
> single assembly called ignite-accelerator. This will be advantageous for 
> downstream integrators like Bigtop, where all bits can be packaged together, 
> tested, and deployed with proper configurations and permissions to avoid 
> interoperability issues. A typical is when spark-shell starts an Ignite node 
> which crashes because user 'spark' isn't allowed to write into Ignite's 
> work-dir, etc.



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

[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle assembly for downstream consumption.

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated IGNITE-1555:
---
Attachment: IGNITE-1555.patch

> Combine ignite-hadoop and ignite-spark into signle assembly for downstream 
> consumption.
> ---
>
> Key: IGNITE-1555
> URL: https://issues.apache.org/jira/browse/IGNITE-1555
> Project: Ignite
>  Issue Type: New Feature
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 1.5
>
> Attachments: IGNITE-1555.patch, IGNITE-1555.patch, IGNITE-1555.patch, 
> IGNITE-1555.patch
>
>
> Let's combine all nice things that Ignite provides for Hadoop and Spark into 
> single assembly called ignite-accelerator. This will be advantageous for 
> downstream integrators like Bigtop, where all bits can be packaged together, 
> tested, and deployed with proper configurations and permissions to avoid 
> interoperability issues. A typical is when spark-shell starts an Ignite node 
> which crashes because user 'spark' isn't allowed to write into Ignite's 
> work-dir, etc.



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

[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-1146 at 10/13/15 3:50 AM:
--

1),2),5) - tested
A new ticket was filed for 4)


was (Author: pkonstantinov):
1),2),5) - tested

> Implement summary page with configuration downloads.
> 
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
> Fix For: 1.5
>
> Attachments: summary - client.png, summary - server.png, 
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.



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

[jira] [Resolved] (IGNITE-1146) Implement summary page with configuration downloads.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-1146.

Resolution: Fixed

> Implement summary page with configuration downloads.
> 
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 1.5
>
> Attachments: summary - client.png, summary - server.png, 
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.



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

[jira] [Closed] (IGNITE-1146) Implement summary page with configuration downloads.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-1146.
--
Assignee: (was: Andrey Novikov)

> Implement summary page with configuration downloads.
> 
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
> Fix For: 1.5
>
> Attachments: summary - client.png, summary - server.png, 
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.



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

[jira] [Updated] (IGNITE-1658) Detecting of agent works incorrectly when switching notebooks

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-1658:
---
Summary: Detecting of agent works incorrectly when switching notebooks  
(was: Detecting of agent works incorrect when switching notebook)

> Detecting of agent works incorrectly when switching notebooks
> -
>
> Key: IGNITE-1658
> URL: https://issues.apache.org/jira/browse/IGNITE-1658
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
>
> Create two notebooks and switch from one to another.



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

[jira] [Closed] (IGNITE-1634) We should generate POJO classes in Client configuration too

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-1634.
--
Assignee: (was: Pavel Konstantinov)

Successfully tested.

> We should generate POJO classes in Client configuration too
> ---
>
> Key: IGNITE-1634
> URL: https://issues.apache.org/jira/browse/IGNITE-1634
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Currently we do not generate POJO for Client.



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

[jira] [Resolved] (IGNITE-1148) Implement sql query to ignite node.

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-1148.

Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Andrey Novikov)

> Implement sql query to ignite node.
> ---
>
> Key: IGNITE-1148
> URL: https://issues.apache.org/jira/browse/IGNITE-1148
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: metadata mockup.png, sql - notebooks.png
>
>
> Need create page for display sql query result:
> * Add optional select cache.
> * Scan query
> * Explain query
> * Query
> * Show metadata.
> Connect with agent through websocket. 



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

[jira] [Resolved] (IGNITE-1649) TcpDiscoverySpi configuraiton in cluster configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-1649.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> TcpDiscoverySpi configuraiton in cluster configuration
> --
>
> Key: IGNITE-1649
> URL: https://issues.apache.org/jira/browse/IGNITE-1649
> Project: Ignite
>  Issue Type: Sub-task
>  Components: website
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> # Add configuration of TcpDiscoverySpi on cluster configuration page.
> # Add configuration of TcpCommunicationSpi on cluster configuration page.



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

[jira] [Assigned] (IGNITE-1257) Implement agent download dialog for page with such functionality

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-1257:
-

Assignee: Andrey Novikov  (was: Vasiliy Sisko)

> Implement agent download dialog for page with such functionality
> 
>
> Key: IGNITE-1257
> URL: https://issues.apache.org/jira/browse/IGNITE-1257
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> * Implement common agent download dialog as template use load from metadata 
> dialog.
> * Generate agent archive with properties file filled by user and server 
> settings (for zero configuration run of agent).
> * Use token instead of login, password in agent configuration.



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

[jira] [Created] (IGNITE-1658) Detecting of agent works incorrect when switching notebook

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-1658:
--

 Summary: Detecting of agent works incorrect when switching notebook
 Key: IGNITE-1658
 URL: https://issues.apache.org/jira/browse/IGNITE-1658
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko


Create two notebooks and switch from one to another.



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

[jira] [Resolved] (IGNITE-1177) Implement metadata screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-1177.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Fixed.

> Implement metadata screen
> -
>
> Key: IGNITE-1177
> URL: https://issues.apache.org/jira/browse/IGNITE-1177
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Implement metadata screen that should:
> 1) Add/edit metadata manually.
> 2) Import metadata from database metadata.



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

[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-1177 at 10/13/15 4:31 AM:
-

Fixed tooltip.


was (Author: vsisko):
Fixed.

> Implement metadata screen
> -
>
> Key: IGNITE-1177
> URL: https://issues.apache.org/jira/browse/IGNITE-1177
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Implement metadata screen that should:
> 1) Add/edit metadata manually.
> 2) Import metadata from database metadata.



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

[jira] [Created] (IGNITE-1657) Spontaneous scrolling of summary page

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-1657:
--

 Summary: Spontaneous scrolling of summary page
 Key: IGNITE-1657
 URL: https://issues.apache.org/jira/browse/IGNITE-1657
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov


Note: this is copied from IGNITE-1146. We have no idea right now how to fix it.
--
I scrolled the page up so that Client section was at the top of the screen. 
Then switched Client preview to Java view - the page is scrolling down. 



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