[jira] [Commented] (IGNITE-6041) Update Gettting Started documentation page

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6041:
-

Added the SQL example for now:
https://apacheignite.readme.io/v2.1/docs/getting-started#first-ignite-sql-application

The rest is being reworked on a hidden documentation page:
https://apacheignite.readme.io/v2.1/docs/getting-started-in-progress

> Update Gettting Started documentation page
> --
>
> Key: IGNITE-6041
> URL: https://issues.apache.org/jira/browse/IGNITE-6041
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Akmal Chaudhri
>  Labels: docs
>
> Update Getting Started guide in the documentation [1]:
> # show enable/disable persistence flag
> # add SQL connectivity example (create, insert, select)
> # put data grid example right after SQL
> # add collocated computation example to the data grid example
> # add service grid example
> [1] https://apacheignite.readme.io/docs/getting-started



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

[jira] [Assigned] (IGNITE-6041) Update Gettting Started documentation page

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-6041:
---

Assignee: Denis Magda  (was: Akmal Chaudhri)

> Update Gettting Started documentation page
> --
>
> Key: IGNITE-6041
> URL: https://issues.apache.org/jira/browse/IGNITE-6041
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Denis Magda
>  Labels: docs
>
> Update Getting Started guide in the documentation [1]:
> # show enable/disable persistence flag
> # add SQL connectivity example (create, insert, select)
> # put data grid example right after SQL
> # add collocated computation example to the data grid example
> # add service grid example
> [1] https://apacheignite.readme.io/docs/getting-started



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

[jira] [Assigned] (IGNITE-5739) JVM crash on node deactivation

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5739:


Assignee: Semen Boikov  (was: Alexey Kuznetsov)

[~pkonstantinov] Can you prepare reproducer?

> JVM crash on node deactivation
> --
>
> Key: IGNITE-5739
> URL: https://issues.apache.org/jira/browse/IGNITE-5739
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Semen Boikov
> Fix For: 2.2
>
> Attachments: hs_err_pid16076.log, ignite-c43368bb.log
>
>
> Start one node (with persistence).
> Activate
> Deactivate - node crashed.



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

[jira] [Closed] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-5985.
--

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Commented] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5985:


Closed.

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Resolved] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-5985.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Setting both QueryEntity.KeyFieldName &  QueryEntity.KeyFields is a correct 
case.
`KeyFieldName ` used for SELECT and `KeyFields` DML (INSERT, for example).

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Updated] (IGNITE-6182) Change default max memory size from 80% to 20%

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6182:

Priority: Blocker  (was: Critical)

> Change default max memory size from 80% to 20%
> --
>
> Key: IGNITE-6182
> URL: https://issues.apache.org/jira/browse/IGNITE-6182
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
>Priority: Blocker
> Fix For: 2.2
>
>
> Currently we can allocate up to 80% of available RAM by default. It could 
> lead to swap with potential risk of hang.
> In order to improve user experience, we need to do the following:
> 1) Decrease default to 20% 
> ({{MemoryConfiguration.DFLT_MEMORY_POLICY_FRACTION}})
> 2) When node starts it should sum max sizes of all memory regions plus Java's 
> XMX. If result is greater than 50% of total RAM, we should issue a warning 
> about potential swap.



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

[jira] [Commented] (IGNITE-6167) Ability to set custom SSLServerSocketFactory and SSLSocketFactory or enabled TLS protocols and cipher suites

[Jens Borgland (JIRA)]

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

Jens Borgland commented on IGNITE-6167:
---

Thank you [~ilyak]! I did at some point explore this option but I didn't think 
of delegating to the SSLContext from my SSLContextSpi implementation (and I 
couldn't find a way of getting hold of a SSLContextSpi instance). I've now done 
just the thing you suggested and through that also worked around IGNITE-6168.

> Ability to set custom SSLServerSocketFactory and SSLSocketFactory or enabled 
> TLS protocols and cipher suites
> 
>
> Key: IGNITE-6167
> URL: https://issues.apache.org/jira/browse/IGNITE-6167
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Jens Borgland
>
> It would be very useful to be able to, in addition to the 
> {{javax.net.ssl.SSLContext}}, either specify a custom 
> {{javax.net.ssl.SSLServerSocketFactory}} and a custom 
> {{javax.net.ssl.SSLSocketFactory}}, or to be able to at least specify the 
> enabled TLS protocols and cipher suites.
> I have noticed that the 
> {{org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter}} has support for 
> the latter but I cannot find a way of getting a reference to the filter 
> instance. The {{GridNioSslFilter}} also isn't used by {{TcpDiscoverySpi}} as 
> far as I can tell.
> Currently (as far as I can tell) there is no way of specifying the enabled 
> cipher suites and protocols used by Ignite, without doing it globally for the 
> JRE.



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

[jira] [Closed] (IGNITE-6039) Update Persistence page on the website

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-6039.
---

> Update Persistence page on the website
> --
>
> Key: IGNITE-6039
> URL: https://issues.apache.org/jira/browse/IGNITE-6039
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Prachi Garg
>  Labels: site
>
> # add Write-Ahead-Log (WAL) sub-section
> # add Main Storage sub-section
> # add Checkpointing sub-section
> # add Redundancy sub-section (describe backups)
> # add Durability sub-section (describe restarts)
> # add Configuration example
> # provide a better diagram if possible



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

[jira] [Created] (IGNITE-6182) Change default max memory size from 80% to 20%

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6182:
---

 Summary: Change default max memory size from 80% to 20%
 Key: IGNITE-6182
 URL: https://issues.apache.org/jira/browse/IGNITE-6182
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 2.1
Reporter: Vladimir Ozerov
Assignee: Igor Seliverstov
Priority: Critical
 Fix For: 2.2


Currently we can allocate up to 80% of available RAM by default. It could lead 
to swap with potential risk of hang.

In order to improve user experience, we need to do the following:
1) Decrease default to 20% ({{MemoryConfiguration.DFLT_MEMORY_POLICY_FRACTION}})
2) When node starts it should sum max sizes of all memory regions plus Java's 
XMX. If result is greater than 50% of total RAM, we should issue a warning 
about potential swap.



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

[jira] [Created] (IGNITE-6181) Tx is not rolled back on timeout leading to potential whole grid hang

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-6181:
-

 Summary: Tx is not rolled back on timeout leading to potential 
whole grid hang
 Key: IGNITE-6181
 URL: https://issues.apache.org/jira/browse/IGNITE-6181
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Alexei Scherbakov
 Fix For: 2.3


Unit test reproducer:

{noformat}
/*
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
 * The ASF licenses this file to You under the Apache License, Version 2.0
 * (the "License"); you may not use this file except in compliance with
 * the License.  You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.apache.ignite.cache;

import java.util.concurrent.CountDownLatch;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.atomic.AtomicBoolean;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteException;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.TransactionConfiguration;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;

/**
 * Tests ability to rollback not properly closed transaction.
 */
public class IgniteTxTimeoutTest extends GridCommonAbstractTest {
/** */
private static final long TX_TIMEOUT = 3_000L;

/** */
private static final String CACHE_NAME = "test";

/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new 
TcpDiscoveryVmIpFinder(true);

/** */
private final CountDownLatch l = new CountDownLatch(1);

/** */
private final Object mux = new Object();

/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String 
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);

cfg.setDiscoverySpi(new TcpDiscoverySpi().setIpFinder(IP_FINDER));

TransactionConfiguration txCfg = new TransactionConfiguration();
txCfg.setDefaultTxTimeout(TX_TIMEOUT);

cfg.setTransactionConfiguration(txCfg);

CacheConfiguration ccfg = new CacheConfiguration(CACHE_NAME);
ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);

cfg.setCacheConfiguration(ccfg);

return cfg;
}

/** */
public void testTxTimeoutHandling() throws Exception {
try {
final Ignite ignite = startGrid();

final AtomicBoolean released = new AtomicBoolean();

multithreadedAsync(new Runnable() {
@Override public void run() {
// Start tx with default settings.
try (Transaction tx = ignite.transactions().txStart()) {
ignite.cache(CACHE_NAME).put(1, 1);

l.countDown();

// Wait longer than default timeout.
synchronized (mux) {
while (!released.get()) {
try {
mux.wait();
}
catch (InterruptedException e) {
throw new IgniteException(e);
}
}
}

try {
tx.commit();

fail();
}
catch (IgniteException e) {
// Expect exception - tx is rolled back.
}
}
}
}, 1, "Locker");

IgniteInternalFuture fut2 = multithreadedAsync(new Runnable() {
@Override public void run() {
U.awaitQuiet(l);

// Try to acquire lock.
// Acquisition will be 

[jira] [Updated] (IGNITE-6180) Marshaller mappings are not restored from disk on node start

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-6180:

Attachment: BinaryOnJoinedNodeTest.java

> Marshaller mappings are not restored from disk on node start
> 
>
> Key: IGNITE-6180
> URL: https://issues.apache.org/jira/browse/IGNITE-6180
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.2
>
> Attachments: BinaryOnJoinedNodeTest.java
>
>
> h2. Steps to reproduce
> # Start node1 with persistence enabled.
> # Put instance of custom class to cache so marshaller mapping for the class 
> is created.
> # Restart node1.
> # Start node2 and ensure it joins the cluster with node1.
> # Get instance from cache on node2 added on step #2.
> h2. Expected behavior
> Instance is retrieved and deserialized successfully.
> h2. Actual behavior
> Exception is thrown, no instance is retrieved from cache.
> {noformat}
> Caused by: java.lang.ClassNotFoundException: Unknown pair [platformId=0, 
> typeId=-347776464]
>   at 
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(MarshallerContextImpl.java:392)
>   at 
> org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:342)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:686)
>   ... 15 more
> {noformat}
> JUnit test is attached to the ticket.



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

[jira] [Created] (IGNITE-6180) Marshaller mappings are not restored from disk on node start

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-6180:
---

 Summary: Marshaller mappings are not restored from disk on node 
start
 Key: IGNITE-6180
 URL: https://issues.apache.org/jira/browse/IGNITE-6180
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.2


h2. Steps to reproduce
# Start node1 with persistence enabled.
# Put instance of custom class to cache so marshaller mapping for the class is 
created.
# Restart node1.
# Start node2 and ensure it joins the cluster with node1.
# Get instance from cache on node2 added on step #2.

h2. Expected behavior
Instance is retrieved and deserialized successfully.

h2. Actual behavior
Exception is thrown, no instance is retrieved from cache.
{noformat}
Caused by: java.lang.ClassNotFoundException: Unknown pair [platformId=0, 
typeId=-347776464]
at 
org.apache.ignite.internal.MarshallerContextImpl.getClassName(MarshallerContextImpl.java:392)
at 
org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:342)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:686)
... 15 more
{noformat}

JUnit test is attached to the ticket.



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

[jira] [Updated] (IGNITE-6138) JDBC driver metadata queries operate on cache/type instead of schema/table

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-6138:

Description: 
It has to use toUpperCase() to address the mismatch which isn't a correct 
approach

Some additional information should be passed down from MetadataTask in 
GridCacheSqlMetadata.

Also fetch actual name for primary key and use that if possible.

  was:
It has to use toUpperCase() to address the mismatch which isn't a correct 
approach

Some additional information should be passed down from MetadataTask in 
GridCacheSqlMetadata.


> JDBC driver metadata queries operate on cache/type instead of schema/table
> --
>
> Key: IGNITE-6138
> URL: https://issues.apache.org/jira/browse/IGNITE-6138
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>
> It has to use toUpperCase() to address the mismatch which isn't a correct 
> approach
> Some additional information should be passed down from MetadataTask in 
> GridCacheSqlMetadata.
> Also fetch actual name for primary key and use that if possible.



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

[jira] [Commented] (IGNITE-6175) JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6175:
-

LGTM. Merged to master branch.

> JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite
> ---
>
> Key: IGNITE-6175
> URL: https://issues.apache.org/jira/browse/IGNITE-6175
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Andrey Gura
> Fix For: 2.2
>
>
> JVM crash dump and logs you could find here
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteBinarySImpleMapperBasic=785893_Ignite20Tests_IgniteBinarySImpleMapperBasic=pull/2380/head
> {code}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f6a0274a13f, pid=3507, tid=140092082124544
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 
> 1.7.0_80-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # J 10572 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readLock(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;)J
>  (39 bytes) @ 0x7f6a0274a13f [0x7f6a02749ba0+0x59f]
> #
> # Core dump written. Default location: 
> /data/teamcity/work/820be461cd64b574/core or core.3507
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> # {code}



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

[jira] [Commented] (IGNITE-5855) SQL: BigInteger support broken in SQL queries.

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-5855:
-

[~vozerov] please take a look.

> SQL: BigInteger support broken in SQL queries.
> --
>
> Key: IGNITE-5855
> URL: https://issues.apache.org/jira/browse/IGNITE-5855
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0, 2.1
>Reporter: Andrew Mashenkov
>Assignee: Ilya Kasnacheev
> Fix For: 2.2
>
> Attachments: BigIntegerKeySqlTest.java
>
>
> Looks like BigInteger support in SQL was broken.
> It works fine on ignite-1.9
> PFA reproducer.



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

[jira] [Commented] (IGNITE-5855) SQL: BigInteger support broken in SQL queries.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5855:


GitHub user alamar opened a pull request:

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

IGNITE-5855 Type-safe parameters setting fixes crash when querying 
BigInteger key



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

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

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

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


commit 643f2e58415525a75c3630f8d2f174065db9a0e0
Author: Ilya Kasnacheev 
Date:   2017-08-24T16:17:04Z

IGNITE-5855 Type-safe parameters setting fixes crash when querying 
BigInteger key




> SQL: BigInteger support broken in SQL queries.
> --
>
> Key: IGNITE-5855
> URL: https://issues.apache.org/jira/browse/IGNITE-5855
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0, 2.1
>Reporter: Andrew Mashenkov
>Assignee: Ilya Kasnacheev
> Fix For: 2.2
>
> Attachments: BigIntegerKeySqlTest.java
>
>
> Looks like BigInteger support in SQL was broken.
> It works fine on ignite-1.9
> PFA reproducer.



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

[jira] [Commented] (IGNITE-5855) SQL: BigInteger support broken in SQL queries.

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-5855:
-

The offender here is H2's ValueDecimal class:

It doesn't override Value's covertTo(), so when it is asked to be converted to 
Java object, it returns
{code}
return ValueJavaObject.getNoCopy(null,
StringUtils.convertHexToBytes(getString().trim()), 
getDataHandler());
{code}

Instead of sensible "if (targetType == JAVA_OBJECT) return value;" as one might 
imagine.

So we will have to do the check outside of H2 code.


> SQL: BigInteger support broken in SQL queries.
> --
>
> Key: IGNITE-5855
> URL: https://issues.apache.org/jira/browse/IGNITE-5855
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0, 2.1
>Reporter: Andrew Mashenkov
>Assignee: Ilya Kasnacheev
> Fix For: 2.2
>
> Attachments: BigIntegerKeySqlTest.java
>
>
> Looks like BigInteger support in SQL was broken.
> It works fine on ignite-1.9
> PFA reproducer.



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

[jira] [Comment Edited] (IGNITE-6175) JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-6175 at 8/24/17 3:43 PM:
--

[~EdShangGG] Why your cycle tests {{stop}} variable for {{true}} value while it 
is initialized to {{false}} value before test is started? It seems that cycle 
doesn't execute any iteration.


was (Author: agura):
[~EdShangGG] Why your cycle tests {{stop}} variable for {{true}} value while it 
initialized to {{false}} value before test is started? It seems that cycle 
doesn't execute any iteration.

> JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite
> ---
>
> Key: IGNITE-6175
> URL: https://issues.apache.org/jira/browse/IGNITE-6175
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Andrey Gura
> Fix For: 2.2
>
>
> JVM crash dump and logs you could find here
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteBinarySImpleMapperBasic=785893_Ignite20Tests_IgniteBinarySImpleMapperBasic=pull/2380/head
> {code}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f6a0274a13f, pid=3507, tid=140092082124544
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 
> 1.7.0_80-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # J 10572 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readLock(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;)J
>  (39 bytes) @ 0x7f6a0274a13f [0x7f6a02749ba0+0x59f]
> #
> # Core dump written. Default location: 
> /data/teamcity/work/820be461cd64b574/core or core.3507
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> # {code}



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

[jira] [Created] (IGNITE-6179) Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-6179:
--

 Summary: Test fail 
DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
 Key: IGNITE-6179
 URL: https://issues.apache.org/jira/browse/IGNITE-6179
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Dmitriy Govorukhin
Priority: Critical
 Fix For: 2.2


Test fail with assertion 
{code}
[2017-08-24 
18:34:06,207][ERROR][tcp-client-disco-msg-worker-#61%index.DynamicIndexReplicatedAtomicConcurrentSelfTest4%][IgniteClientReconnectAbstractTest$TestTcpDiscoverySpi]
 Failed to unmarshal discovery custom message.
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onSchemaFinishDiscovery(GridQueryProcessor.java:498)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onDiscovery(GridQueryProcessor.java:894)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:2906)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:660)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:560)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2391)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processCustomMessage(ClientImpl.java:2297)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1874)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1758)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}



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

[jira] [Updated] (IGNITE-6179) Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-6179:
---
Attachment: log

> Test fail 
> DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
> 
>
> Key: IGNITE-6179
> URL: https://issues.apache.org/jira/browse/IGNITE-6179
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.2
>
> Attachments: log
>
>
> Test fail with assertion 
> {code}
> [2017-08-24 
> 18:34:06,207][ERROR][tcp-client-disco-msg-worker-#61%index.DynamicIndexReplicatedAtomicConcurrentSelfTest4%][IgniteClientReconnectAbstractTest$TestTcpDiscoverySpi]
>  Failed to unmarshal discovery custom message.
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onSchemaFinishDiscovery(GridQueryProcessor.java:498)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onDiscovery(GridQueryProcessor.java:894)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:2906)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:660)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:560)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2391)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processCustomMessage(ClientImpl.java:2297)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1874)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1758)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}



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

[jira] [Comment Edited] (IGNITE-6175) JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-6175 at 8/24/17 3:34 PM:
--

[~EdShangGG] Why your cycle tests {{stop}} variable for {{true}} value while it 
initialized to {{false}} value before test is started? It seems that cycle 
doesn't execute any iteration.


was (Author: agura):
[~EdShangGG] Why your cycle test {{stop}} variable for {{true}} value while it 
initialized to {{false}} value before test is started? It seems that cycle 
doesn't execute any iteration.

> JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite
> ---
>
> Key: IGNITE-6175
> URL: https://issues.apache.org/jira/browse/IGNITE-6175
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Andrey Gura
> Fix For: 2.2
>
>
> JVM crash dump and logs you could find here
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteBinarySImpleMapperBasic=785893_Ignite20Tests_IgniteBinarySImpleMapperBasic=pull/2380/head
> {code}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f6a0274a13f, pid=3507, tid=140092082124544
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 
> 1.7.0_80-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # J 10572 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readLock(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;)J
>  (39 bytes) @ 0x7f6a0274a13f [0x7f6a02749ba0+0x59f]
> #
> # Core dump written. Default location: 
> /data/teamcity/work/820be461cd64b574/core or core.3507
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> # {code}



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

[jira] [Commented] (IGNITE-6178) Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 default in persistent store confguration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6178:


GitHub user glukos opened a pull request:

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

IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 
default in persistent store confguration



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

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

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

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


commit b9246fcb261ce50604ab220e542d879c6c8d8b0d
Author: Ivan Rakov 
Date:   2017-08-24T15:18:31Z

IGNITE-6178 Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 
default in persistent store confguration




> Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 default in 
> persistent store confguration
> 
>
> Key: IGNITE-6178
> URL: https://issues.apache.org/jira/browse/IGNITE-6178
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
> Fix For: 2.2
>
>
> Multithreaded and ordered checkpoints show better performance on most 
> enviroments.



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

[jira] [Commented] (IGNITE-6175) JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6175:
-

[~EdShangGG] Why your cycle test {{stop}} variable for {{true}} value while it 
initialized to {{false}} value before test is started? It seems that cycle 
doesn't execute any iteration.

> JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite
> ---
>
> Key: IGNITE-6175
> URL: https://issues.apache.org/jira/browse/IGNITE-6175
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Andrey Gura
> Fix For: 2.2
>
>
> JVM crash dump and logs you could find here
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteBinarySImpleMapperBasic=785893_Ignite20Tests_IgniteBinarySImpleMapperBasic=pull/2380/head
> {code}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f6a0274a13f, pid=3507, tid=140092082124544
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 
> 1.7.0_80-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # J 10572 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readLock(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;)J
>  (39 bytes) @ 0x7f6a0274a13f [0x7f6a02749ba0+0x59f]
> #
> # Core dump written. Default location: 
> /data/teamcity/work/820be461cd64b574/core or core.3507
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> # {code}



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

[jira] [Created] (IGNITE-6178) Make CheckpointWriteOrder.SEQUENTIAL and checkpointingThreads=4 default in persistent store confguration

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-6178:
--

 Summary: Make CheckpointWriteOrder.SEQUENTIAL and 
checkpointingThreads=4 default in persistent store confguration
 Key: IGNITE-6178
 URL: https://issues.apache.org/jira/browse/IGNITE-6178
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Ivan Rakov
Assignee: Ivan Rakov
 Fix For: 2.2


Multithreaded and ordered checkpoints show better performance on most 
enviroments.



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

[jira] [Updated] (IGNITE-5855) SQL: BigInteger support broken in SQL queries.

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-5855:

Fix Version/s: 2.2

> SQL: BigInteger support broken in SQL queries.
> --
>
> Key: IGNITE-5855
> URL: https://issues.apache.org/jira/browse/IGNITE-5855
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0, 2.1
>Reporter: Andrew Mashenkov
>Assignee: Ilya Kasnacheev
> Fix For: 2.2
>
> Attachments: BigIntegerKeySqlTest.java
>
>
> Looks like BigInteger support in SQL was broken.
> It works fine on ignite-1.9
> PFA reproducer.



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

[jira] [Assigned] (IGNITE-5855) SQL: BigInteger support broken in SQL queries.

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev reassigned IGNITE-5855:
---

Assignee: Ilya Kasnacheev  (was: Sergey Kalashnikov)

> SQL: BigInteger support broken in SQL queries.
> --
>
> Key: IGNITE-5855
> URL: https://issues.apache.org/jira/browse/IGNITE-5855
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0, 2.1
>Reporter: Andrew Mashenkov
>Assignee: Ilya Kasnacheev
> Attachments: BigIntegerKeySqlTest.java
>
>
> Looks like BigInteger support in SQL was broken.
> It works fine on ignite-1.9
> PFA reproducer.



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

[jira] [Commented] (IGNITE-6130) JDBC Thin: JdbcThinResultSet must support types conversions

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-6130:
--

Waits for [tests 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2510%2Fhead].

> JDBC Thin: JdbcThinResultSet must support types conversions 
> 
>
> Key: IGNITE-6130
> URL: https://issues.apache.org/jira/browse/IGNITE-6130
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>
> Now JdbcThinResultSet  doesn't support data types transformation.
> e.g.: if the attribute type is SHORT
> all the methods below must return valid value:
> {{getByte, getShort, getInt, getLong, getFloat, getDouble, getBigDecimal, 
> getBoolean, getString, getNString}}
> See the table *B-6* at the JDBC spec (see also [8.9.5 and 
> 8.9.6|http://docs.oracle.com/javase/6/docs/technotes/guides/jdbc/getstart/mapping.html#996857]).



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

[jira] [Commented] (IGNITE-6130) JDBC Thin: JdbcThinResultSet must support types conversions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6130:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-6130 JDBC Thin: JdbcThinResultSet must support types conversions



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

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

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

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


commit 99a02afab6248bb32e2bb5cda4f7d595ec04c62c
Author: tledkov-gridgain 
Date:   2017-08-24T12:57:17Z

IGNITE-6130 JDBC Thin: JdbcThinResultSet must support types conversions




> JDBC Thin: JdbcThinResultSet must support types conversions 
> 
>
> Key: IGNITE-6130
> URL: https://issues.apache.org/jira/browse/IGNITE-6130
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>
> Now JdbcThinResultSet  doesn't support data types transformation.
> e.g.: if the attribute type is SHORT
> all the methods below must return valid value:
> {{getByte, getShort, getInt, getLong, getFloat, getDouble, getBigDecimal, 
> getBoolean, getString, getNString}}
> See the table *B-6* at the JDBC spec (see also [8.9.5 and 
> 8.9.6|http://docs.oracle.com/javase/6/docs/technotes/guides/jdbc/getstart/mapping.html#996857]).



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

[jira] [Created] (IGNITE-6177) Update docs for integration with Apache Zeppelin

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6177:


 Summary: Update docs for integration with Apache Zeppelin
 Key: IGNITE-6177
 URL: https://issues.apache.org/jira/browse/IGNITE-6177
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.2


Since release AI 1.1 we haven't updated the following documentation section:
https://apacheignite.readme.io/v1.1/docs/data-analysis-with-apache-zeppelin



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

[jira] [Commented] (IGNITE-5655) Introduce pluggable string encoder/decoder

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-5655:
--

[~vozerov], thanks for your comments.

As for ignoring encoding byte in binary fields comparison (#7), it works 
without changes right now, since we have only one non-UTF-8 encoding. But it's 
fragile, and I'll fix it, of course.

As for #7.2, we don't need to deserialize fields when encodings match, since we 
just test for equality (as opposed to {{c1.compareTo(c2)}}).

> Introduce pluggable string encoder/decoder
> --
>
> Key: IGNITE-5655
> URL: https://issues.apache.org/jira/browse/IGNITE-5655
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Andrey Kuznetsov
> Fix For: 2.2
>
>
> Currently binary marshaller encodes strings in UTF-8. However, sometimes it 
> makes sense to serialize strings with different encodings to save space. 
> Let's add global property to control String encoding and customize our binary 
> protocol to support it. For instance, we can add another flag 
> {{ENCODED_STRING}}, which will write strings as follows:
> [flag][encoding_flag][str_len][str_bytes]
> First implementation should set preferred encoding for strings in 
> BinaryConfiguration. This setting is optional, default encoding is UTF-8. 
> Currently, the same BinaryConfiguration is used for all cluster nodes, thus 
> no encoding clashes are possible.



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

[jira] [Resolved] (IGNITE-4223) Joining node should fetch affinity for all caches using single message

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-4223.
--
Resolution: Fixed

Fixed as part of IGNITE-6124, now joining node receives affinity as part of 
GridDhtPartitionsFullMessage.

> Joining node should fetch affinity for all caches using single message
> --
>
> Key: IGNITE-4223
> URL: https://issues.apache.org/jira/browse/IGNITE-4223
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 2.2
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Currently when new node joins cluster and 'late affinity assignment' mode is 
> enabled it requests caches affinity using message per cache (see 
> CacheAffinitySharedManager.fetchAffinityOnJoin). Actually in 'late affinity 
> assignment' mode coordinator has affinity information for all caches, so 
> single request can be sent to coordinator.



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

[jira] [Updated] (IGNITE-6176) Request to BinaryMetadataTransport may cause deadlock on grid stop

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-6176:
---
Description: 
We may access BinaryMetadataTransport while holding striped GridCacheIOManager 
lock in some cases (for example, when handling partition exhange message). 
When grid is stopping, BinaryMetadataTransport#requestMetadataUpdate may hang 
on future. This will result a deadlock: this future won't be cancelled during 
grid stop procedure, as we firstly stop GridCacheIOManager (which, in turn, 
requires releasing striped lock).

Steps to reproduce:
1) Remove partition exchange messages from classnames.properties
2) Run IgniteClusterActivateDeactivateTestWithPersistence multiple times

Stacktrace of deadlocked threads:
{noformat}
"sys-#9065%cache.IgniteClusterActivateDeactivateTestWithPersistence4%@18095" 
prio=5 tid=0x2b55 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:432)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:173)
  at 
org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1276)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:783)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteMap(BinaryWriterExImpl.java:786)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:699)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
  at 
org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
  at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9849)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9913)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.prepareMarshal(GridDhtPartitionsSingleMessage.java:289)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1120)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1154)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSinglePartitionRequest(GridDhtPartitionsExchangeFuture.java:2588)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1500(GridDhtPartitionsExchangeFuture.java:114)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2492)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceivePartitionRequest(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionRequest(GridCachePartitionExchangeManager.java:1474)
  at 

[jira] [Updated] (IGNITE-6176) Request to BinaryMetadataTransport may cause deadlock on grid stop

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-6176:
---
Description: 
We may access BinaryMetadataTransport when holding striped GridCacheIOManager 
lock in some cases (for example, when handling partition exhange message). 
When grid is stopping, BinaryMetadataTransport#requestMetadataUpdate may hang 
on future. This will result a deadlock: this future won't be cancelled. as we 
firstly stop GridCacheIOManager (which, in turn, requires releasin striped 
lock).

Steps to reproduce:
1) Remove partition exchange messages from classnames.properties
2) Run IgniteClusterActivateDeactivateTestWithPersistence multiple times

Stacktrace of deadlocked threads:
{noformat}
"sys-#9065%cache.IgniteClusterActivateDeactivateTestWithPersistence4%@18095" 
prio=5 tid=0x2b55 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:432)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:173)
  at 
org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1276)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:783)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteMap(BinaryWriterExImpl.java:786)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:699)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
  at 
org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
  at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9849)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9913)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.prepareMarshal(GridDhtPartitionsSingleMessage.java:289)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1120)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1154)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSinglePartitionRequest(GridDhtPartitionsExchangeFuture.java:2588)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1500(GridDhtPartitionsExchangeFuture.java:114)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2492)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceivePartitionRequest(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionRequest(GridCachePartitionExchangeManager.java:1474)
  at 

[jira] [Updated] (IGNITE-6176) Request to BinaryMetadataTransport may cause deadlock on grid stop

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-6176:
---
Description: 
We may access BinaryMetadataTransport while holding striped GridCacheIOManager 
lock in some cases (for example, when handling partition exhange message). 
When grid is stopping, BinaryMetadataTransport#requestMetadataUpdate may hang 
on future. This will result a deadlock: this future won't be cancelled. as we 
firstly stop GridCacheIOManager (which, in turn, requires releasin striped 
lock).

Steps to reproduce:
1) Remove partition exchange messages from classnames.properties
2) Run IgniteClusterActivateDeactivateTestWithPersistence multiple times

Stacktrace of deadlocked threads:
{noformat}
"sys-#9065%cache.IgniteClusterActivateDeactivateTestWithPersistence4%@18095" 
prio=5 tid=0x2b55 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:432)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:173)
  at 
org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1276)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:783)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteMap(BinaryWriterExImpl.java:786)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:699)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
  at 
org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
  at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9849)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9913)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.prepareMarshal(GridDhtPartitionsSingleMessage.java:289)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1120)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1154)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSinglePartitionRequest(GridDhtPartitionsExchangeFuture.java:2588)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1500(GridDhtPartitionsExchangeFuture.java:114)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2492)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceivePartitionRequest(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionRequest(GridCachePartitionExchangeManager.java:1474)
  at 

[jira] [Updated] (IGNITE-6176) Request to BinaryMetadataTransport may cause deadlock on grid stop

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-6176:
---
Description: 
We may access BinaryMetadataTransport while holding striped GridCacheIOManager 
lock in some cases (for example, when handling partition exhange message). 
When grid is stopping, BinaryMetadataTransport#requestMetadataUpdate may hang 
on future. This will result a deadlock: this future won't be cancelled. as we 
firstly stop GridCacheIOManager (which, in turn, requires releasin striped 
lock).

Steps to reproduce:
1) Remove partition exchange messages from classnames.properties
2) Run IgniteClusterActivateDeactivateTestWithPersistence multiple times

Stacktrace of deadlocked threads:
{noformat}
"sys-#9065%cache.IgniteClusterActivateDeactivateTestWithPersistence4%@18095" 
prio=5 tid=0x2b55 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:432)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:173)
  at 
org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1276)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:783)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteMap(BinaryWriterExImpl.java:786)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:699)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
  at 
org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
  at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9849)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9913)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.prepareMarshal(GridDhtPartitionsSingleMessage.java:289)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1120)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1154)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSinglePartitionRequest(GridDhtPartitionsExchangeFuture.java:2588)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1500(GridDhtPartitionsExchangeFuture.java:114)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2492)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceivePartitionRequest(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionRequest(GridCachePartitionExchangeManager.java:1474)
  at 

[jira] [Created] (IGNITE-6176) Request to BinaryMetadataTransport may cause deadlock on grid stop

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-6176:
--

 Summary: Request to BinaryMetadataTransport may cause deadlock on 
grid stop
 Key: IGNITE-6176
 URL: https://issues.apache.org/jira/browse/IGNITE-6176
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


We may access BinaryMetadataTransport while holding striped GridCacheIOManager 
lock in some cases (for example, during partition exhange). 
When grid is stopping, BinaryMetadataTransport#requestMetadataUpdate may hang 
on future. This will result a deadlock: this future won't be cancelled. as we 
firstly stop GridCacheIOManager (which, in turn, requires releasin striped 
lock).

Steps to reproduce:
1) Remove partition exchange messages from classnames.properties
2) Run IgniteClusterActivateDeactivateTestWithPersistence multiple times

Stacktrace of deadlocked threads:
{noformat}
"sys-#9065%cache.IgniteClusterActivateDeactivateTestWithPersistence4%@18095" 
prio=5 tid=0x2b55 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:432)
  at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:173)
  at 
org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1276)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:783)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteMap(BinaryWriterExImpl.java:786)
  at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:699)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
  at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
  at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:251)
  at 
org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
  at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9849)
  at 
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9913)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.prepareMarshal(GridDhtPartitionsSingleMessage.java:289)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1120)
  at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1154)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSinglePartitionRequest(GridDhtPartitionsExchangeFuture.java:2588)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1500(GridDhtPartitionsExchangeFuture.java:114)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2492)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$6.apply(GridDhtPartitionsExchangeFuture.java:2490)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceivePartitionRequest(GridDhtPartitionsExchangeFuture.java:2490)
  at 

[jira] [Commented] (IGNITE-6175) JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite

[Ivan Rakov (JIRA)]

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

Ivan Rakov commented on IGNITE-6175:


[~EdShangGG], looks good.

> JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite
> ---
>
> Key: IGNITE-6175
> URL: https://issues.apache.org/jira/browse/IGNITE-6175
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Andrey Gura
> Fix For: 2.2
>
>
> JVM crash dump and logs you could find here
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteBinarySImpleMapperBasic=785893_Ignite20Tests_IgniteBinarySImpleMapperBasic=pull/2380/head
> {code}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f6a0274a13f, pid=3507, tid=140092082124544
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 
> 1.7.0_80-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # J 10572 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readLock(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;)J
>  (39 bytes) @ 0x7f6a0274a13f [0x7f6a02749ba0+0x59f]
> #
> # Core dump written. Default location: 
> /data/teamcity/work/820be461cd64b574/core or core.3507
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> # {code}



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

[jira] [Comment Edited] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-5985 at 8/24/17 10:23 AM:
--

Should we allow to set 'Key Field Name' and 'Key Fields' at the same time?
!screenshot-1.png!

Except this all works fine.


was (Author: pkonstantinov):
Should we allow to set 'Key Field Name' and 'Key Fields' at the same time?
!screenshot-1.png!

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Closed] (IGNITE-6127) Web Console: Implement GZip data between web-agent and web server

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-6127.


> Web Console: Implement GZip data between web-agent and web server
> -
>
> Key: IGNITE-6127
> URL: https://issues.apache.org/jira/browse/IGNITE-6127
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> socket.io-client-java does not support compressing for now.
> See: https://github.com/socketio/socket.io-client-java/issues/312
> We can GZip manually for now. 



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

[jira] [Commented] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5985:


Should we allow to set 'Key Field Name' and 'Key Fields' at the same time?
!screenshot-1.png!

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Reopened] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reopened IGNITE-5985:


> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Assigned] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-5985:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Updated] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5985:
---
Attachment: screenshot-1.png

> WebConsole: add generation of keyFields for queryEntity for multiple primary 
> key
> 
>
> Key: IGNITE-5985
> URL: https://issues.apache.org/jira/browse/IGNITE-5985
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> For example, for table like
> {code:java}
> CREATE TABLE TABLE_NAME (
> KEY1 int NOT NULL,
> KEY2 int NOT NULL,
> VALUE int,
> PRIMARY KEY (KEY1,KEY2));
> {code}
> should be generated queryEntity like:
> {code:java}
> 
> 
> 
>  value="org.apache.ignite.examples.TableNameKey"/>
>  value="org.apache.ignite.examples.TableName"/>
> 
> 
> key1
> key2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}



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

[jira] [Resolved] (IGNITE-5805) Fix some alerts identified by lgtm.com

[Malcolm Taylor (JIRA)]

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

Malcolm Taylor resolved IGNITE-5805.

Resolution: Fixed

24 alerts fixed by Semen Boikov

> Fix some alerts identified by lgtm.com
> --
>
> Key: IGNITE-5805
> URL: https://issues.apache.org/jira/browse/IGNITE-5805
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Malcolm Taylor
>Assignee: Malcolm Taylor
> Fix For: 2.2
>
>
> A number of issues have been identified by lgtm.com, detailed at 
> https://lgtm.com/projects/g/apache/ignite/alerts/
> This issue is to address some of the straightforward ones, such as resources 
> not being closed and results of int multiplication being cast to long (with 
> risk of overflow).



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

[jira] [Commented] (IGNITE-6167) Ability to set custom SSLServerSocketFactory and SSLSocketFactory or enabled TLS protocols and cipher suites

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-6167:
-

[~jens.borgland] You can subclass SSLContext and call protected 
SSLContext(SSLContextSpi contextSpi, Provider provider, String protocol) 
constructor with crafted contextSpi which will return 
engineGetServerSocketFactory() with specified TLS protocols and cipher suites. 
Maybe there's some caveat but I don't immediately see it. That sure as day 
requires some dedicated effort.

> Ability to set custom SSLServerSocketFactory and SSLSocketFactory or enabled 
> TLS protocols and cipher suites
> 
>
> Key: IGNITE-6167
> URL: https://issues.apache.org/jira/browse/IGNITE-6167
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Jens Borgland
>
> It would be very useful to be able to, in addition to the 
> {{javax.net.ssl.SSLContext}}, either specify a custom 
> {{javax.net.ssl.SSLServerSocketFactory}} and a custom 
> {{javax.net.ssl.SSLSocketFactory}}, or to be able to at least specify the 
> enabled TLS protocols and cipher suites.
> I have noticed that the 
> {{org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter}} has support for 
> the latter but I cannot find a way of getting a reference to the filter 
> instance. The {{GridNioSslFilter}} also isn't used by {{TcpDiscoverySpi}} as 
> far as I can tell.
> Currently (as far as I can tell) there is no way of specifying the enabled 
> cipher suites and protocols used by Ignite, without doing it globally for the 
> JRE.



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

[jira] [Closed] (IGNITE-4784) Web Console: Revise demo mode

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4784.
--

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



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

[jira] [Commented] (IGNITE-4784) Web Console: Revise demo mode

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4784:


tested

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



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

[jira] [Assigned] (IGNITE-4784) Web Console: Revise demo mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4784:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



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

[jira] [Assigned] (IGNITE-4784) Web Console: Revise demo mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4784:


Assignee: Alexey Kuznetsov  (was: Dmitriy Shabalin)

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



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

[jira] [Closed] (IGNITE-6106) Web console: New function descriptions on homepage carousel and getting started dialog

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6106.
--

> Web console: New function descriptions on homepage carousel and getting 
> started dialog
> --
>
> Key: IGNITE-6106
> URL: https://issues.apache.org/jira/browse/IGNITE-6106
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.2
>
>




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

[jira] [Commented] (IGNITE-6106) Web console: New function descriptions on homepage carousel and getting started dialog

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6106:


Tested.

> Web console: New function descriptions on homepage carousel and getting 
> started dialog
> --
>
> Key: IGNITE-6106
> URL: https://issues.apache.org/jira/browse/IGNITE-6106
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.2
>
>




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

[jira] [Reopened] (IGNITE-4784) Web Console: Revise demo mode

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reopened IGNITE-4784:

  Assignee: Dmitriy Shabalin  (was: Pavel Konstantinov)

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



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

[jira] [Commented] (IGNITE-4784) Web Console: Revise demo mode

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4784:


Got exception in browser (FF)
{code}
Failed to execute collector task. Caches and events can't be shown: 
java.lang.NullPointerException
{code}

in web-agent the following
{code}
Caused by: class org.apache.ignite.IgniteException: Failed to find constructor 
for task argument 
[taskName=org.apache.ignite.internal.visor.node.VisorNodeDataCollectorTask, 
argsCnt=5, args=[true, CONSOLE_lJFPwvtzReD5qrnmclXY, yW7S2F4RixjNVr6XPxEf, 10, 
false]]
at 
org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:400)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1115)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1385)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:640)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:532)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:749)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:505)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:485)
at 
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:227)
... 8 more
{code}

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



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

[jira] [Commented] (IGNITE-6136) Web Console: implement version check

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6136:


Tested.

> Web Console: implement version check
> 
>
> Key: IGNITE-6136
> URL: https://issues.apache.org/jira/browse/IGNITE-6136
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Rework current implementation that check only 1.x, 2.x & 2.1 to universal 
> solution.



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

[jira] [Closed] (IGNITE-6136) Web Console: implement version check

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6136.
--

> Web Console: implement version check
> 
>
> Key: IGNITE-6136
> URL: https://issues.apache.org/jira/browse/IGNITE-6136
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Rework current implementation that check only 1.x, 2.x & 2.1 to universal 
> solution.



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

[jira] [Closed] (IGNITE-6105) Web console: Cache name is missed in preview for cache checkpoint SPI

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6105.
--

> Web console: Cache name is missed in preview for cache checkpoint SPI
> -
>
> Key: IGNITE-6105
> URL: https://issues.apache.org/jira/browse/IGNITE-6105
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: 
> IGNITE_6105_Fixed_generation_of_cache_checkpoint_SPI_.patch
>
>




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

[jira] [Commented] (IGNITE-6105) Web console: Cache name is missed in preview for cache checkpoint SPI

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6105:


Tested.

> Web console: Cache name is missed in preview for cache checkpoint SPI
> -
>
> Key: IGNITE-6105
> URL: https://issues.apache.org/jira/browse/IGNITE-6105
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: 
> IGNITE_6105_Fixed_generation_of_cache_checkpoint_SPI_.patch
>
>




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