[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak commented on IGNITE-1371:
-

Alexey, according the checks for (log != null). The problem with this code 
occurs in a case when you are going to use Ignite in most basic configuration 
without using Spring framework (by configuring and running Ignite in your 
custom code). In a such case the code you written will produce 
NullPointerException.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak commented on IGNITE-1371:
-

According usage of embedded Cassandra for unit tests it's rather hard for me to 
provide estimations. I just found that it doesn't work out of the box, like in 
provided examples. I am rather busy now, so it could take some time to 
investigate the problem.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Created] (IGNITE-2144) [Test] IgniteSemaphore's failover related tests are failing to compile

[Saikat Maitra (JIRA)]

Saikat Maitra created IGNITE-2144:
-

 Summary: [Test] IgniteSemaphore's failover related tests are 
failing to compile
 Key: IGNITE-2144
 URL: https://issues.apache.org/jira/browse/IGNITE-2144
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Saikat Maitra
Priority: Minor


GridCacheAbstractDataStructuresFailoverSelfTest are failing to compile.

Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile 
(default-testCompile) on project ignite-core: Compilation failure: Compilation 
failure:
[ERROR] 
/Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[458,25]
 constructor ConstantTopologyChangeWorker in class 
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
 cannot be applied to given types;
[ERROR] required: int
[ERROR] found: no arguments
[ERROR] reason: actual and formal argument lists differ in length
[ERROR] 
/Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[465,25]
 constructor ConstantTopologyChangeWorker in class 
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
 cannot be applied to given types;
[ERROR] required: int
[ERROR] found: no arguments
[ERROR] reason: actual and formal argument lists differ in length
[ERROR] 
/Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[472,25]
 method multipleTopologyChangeWorker in class 
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
 cannot be applied to given types;
[ERROR] required: int
[ERROR] found: no arguments
[ERROR] reason: actual and formal argument lists differ in length
[ERROR] 
/Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[479,25]
 method multipleTopologyChangeWorker in class 
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
 cannot be applied to given types;
[ERROR] required: int
[ERROR] found: no arguments
[ERROR] reason: actual and formal argument lists differ in length



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

[jira] [Commented] (IGNITE-2144) [Test] IgniteSemaphore's failover related tests are failing to compile

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-2144:
---

I have raised a PR for the compilation issue.

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

> [Test] IgniteSemaphore's failover related tests are failing to compile
> --
>
> Key: IGNITE-2144
> URL: https://issues.apache.org/jira/browse/IGNITE-2144
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Saikat Maitra
>Priority: Minor
>
> GridCacheAbstractDataStructuresFailoverSelfTest are failing to compile.
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile 
> (default-testCompile) on project ignite-core: Compilation failure: 
> Compilation failure:
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[458,25]
>  constructor ConstantTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[465,25]
>  constructor ConstantTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[472,25]
>  method multipleTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[479,25]
>  method multipleTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length



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

[jira] [Created] (IGNITE-2145) Async cache operations on primary node might block

[Avihai Berkovitz (JIRA)]

Avihai Berkovitz created IGNITE-2145:


 Summary: Async cache operations on primary node might block
 Key: IGNITE-2145
 URL: https://issues.apache.org/jira/browse/IGNITE-2145
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4
 Environment: Windows 8.1 64 bit
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
Ignite 1.4.0
Reporter: Avihai Berkovitz


When executing async operations on caches the initial function call is supposed 
to return immediately, without regard to cache state, network traffic, etc. If 
we reference a cache key on a different node it works. But if the primary node 
for a cache key is the same node that initiate the operation everything is 
executed synchronously.
This is probably an optimization, but can have side effects. For example, if a 
long running CacheProcessor is invoked on this key, every operation will block.

Here is some code to illustrate the problem. Notice that there is a 4 seconds 
delay between "Before async op" and "After async op". If you reverse the 
isPrimary() condition it won't happen.

{code}
IgniteConfiguration igniteConfiguration = new IgniteConfiguration()
.setFailoverSpi(new AlwaysFailoverSpi())
.setGridLogger(new Slf4jLogger())
.setPeerClassLoadingEnabled(false)
.setDeploymentMode(DeploymentMode.CONTINUOUS);
Ignite ignite1 = Ignition.start(igniteConfiguration);
Ignite ignite2 = Ignition.start(igniteConfiguration.setGridName("2"));
assert ignite1.cluster().nodes().size() == 2;
assert ignite2.cluster().nodes().size() == 2;

CacheConfiguration cacheConfiguration = new 
CacheConfiguration()
.setName("test")
.setCacheMode(CacheMode.PARTITIONED)
.setAtomicityMode(CacheAtomicityMode.ATOMIC)

.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
IgniteCache cache1 = 
ignite1.getOrCreateCache(cacheConfiguration);
IgniteCache cache2 = 
ignite2.getOrCreateCache(cacheConfiguration);

// Find key mapped to the first node
String key = IntStream.range(0, 100)
.mapToObj(value -> "HI" + value)
.filter(s -> 
ignite1.affinity(cacheConfiguration.getName()).isPrimary(ignite1.cluster().localNode(),
 s))
.findFirst().get();

// Run a blocked processor from node 2
Thread thread = new Thread() {
@Override
public void run() {
System.out.println("Invoking blocked processor");

cache2.invoke(key, (entry, arguments) -> {
System.out.println("IN INVOKE");
try {
Thread.sleep(5 * 1000);
} catch (InterruptedException e) {
e.printStackTrace();
}
return null;
});

System.out.println("Blocked invoke returned");
}
};

thread.start();
Thread.sleep(1000);

IgniteCache async1 = cache1.withAsync();

System.out.println("Before async op");
//async1.put(key, 1);
//async1.get(key);
async1.containsKey(key);
System.out.println("After async op");
assert async1.future().isDone();

thread.join();
ignite2.close();
ignite1.close();
{code}



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

[jira] [Commented] (IGNITE-2144) [Test] IgniteSemaphore's failover related tests are failing to compile

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-2144:
---

Please assign this jira ticket to me.

> [Test] IgniteSemaphore's failover related tests are failing to compile
> --
>
> Key: IGNITE-2144
> URL: https://issues.apache.org/jira/browse/IGNITE-2144
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Saikat Maitra
>Priority: Minor
>
> GridCacheAbstractDataStructuresFailoverSelfTest are failing to compile.
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile 
> (default-testCompile) on project ignite-core: Compilation failure: 
> Compilation failure:
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[458,25]
>  constructor ConstantTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[465,25]
>  constructor ConstantTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[472,25]
>  method multipleTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[479,25]
>  method multipleTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length



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

[jira] [Commented] (IGNITE-435) Visor should use smart format for time values

[YoungGyu Chun (JIRA)]

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

YoungGyu Chun commented on IGNITE-435:
--

I am working on it

> Visor should use smart format for time values
> -
>
> Key: IGNITE-435
> URL: https://issues.apache.org/jira/browse/IGNITE-435
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Priority: Minor
>
> {code}
>  Maximum job execute time| 60009ms  - should show 1m
>  Curent job execute time | 120ms
>  Average job execute time| 1126.57ms - should show 1s
>  Total busy time | 70769ms - should show 1m 10s
> {code}
> Also please fix the typo 'Curent' - should be 'Current'



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

[jira] [Comment Edited] (IGNITE-435) Visor should use smart format for time values

[YoungGyu Chun (JIRA)]

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

YoungGyu Chun edited comment on IGNITE-435 at 12/13/15 1:05 PM:


I am working on it. 
please give me a permission to change the state of of this ticket


was (Author: jun562):
I am working on it

> Visor should use smart format for time values
> -
>
> Key: IGNITE-435
> URL: https://issues.apache.org/jira/browse/IGNITE-435
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Priority: Minor
>
> {code}
>  Maximum job execute time| 60009ms  - should show 1m
>  Curent job execute time | 120ms
>  Average job execute time| 1126.57ms - should show 1s
>  Total busy time | 70769ms - should show 1m 10s
> {code}
> Also please fix the typo 'Curent' - should be 'Current'



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

[jira] [Created] (IGNITE-2146) Service deployment using a cache-accessing-predicate in node filter sometimes causes a deadlock

[Noam Liran (JIRA)]

Noam Liran created IGNITE-2146:
--

 Summary: Service deployment using a cache-accessing-predicate in 
node filter sometimes causes a deadlock
 Key: IGNITE-2146
 URL: https://issues.apache.org/jira/browse/IGNITE-2146
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4, 1.5
 Environment: Mac OS X 10.11
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
Ignite 1.4.0 + Ignite-1.5.0-b1
Reporter: Noam Liran


We're deploying a service on a cluster group. The cluster group is filtered 
using a predicate. The predicate accesses a cache key to determine if it should 
return true for a node or not.

If a new node joins the cluster while the predicate is running a deadlock is 
encountered: cache functions do not return and the node does not finish joining 
the cluster.

I've created a sample program to reproduce this on 1.4.0 and also tried to 
reproduce it on 1.5.0-b1;
On 1.4.0 the deadlock is usually reproduced, on 1.5.0-b1 it might take a few 
tries (I'm guessing it's a timing issue.. I tried to improve the odds of 
reproduction by using a countdown latch).

Code:
{code:title=Main.java}
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.Ignition;
import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheWriteSynchronizationMode;
import org.apache.ignite.cluster.ClusterGroup;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.services.Service;
import org.apache.ignite.services.ServiceContext;

import java.util.concurrent.CountDownLatch;

/**
 * Created by noliran on 08/12/2015.
 */
public class Main {
public static IgniteCache cache1;
public static CountDownLatch latch = new CountDownLatch(1);

public static CacheConfiguration CACHE_CONFIG = new 
CacheConfiguration()
.setName("testCache")
.setAtomicityMode(CacheAtomicityMode.ATOMIC)
.setCacheMode(CacheMode.REPLICATED)

.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
.setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY);

public static void main(String[] args) throws InterruptedException {
IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
Ignite ignite1 = 
Ignition.start(igniteConfiguration.setGridName("grid1"));

System.out.println("Creating cache");
cache1 = ignite1.getOrCreateCache(CACHE_CONFIG);

ClusterGroup group = ignite1.cluster().forPredicate(node -> {
System.out.println("predicate: starting");
latch.countDown();

try {
System.out.println("predicate: before sleep");
Thread.sleep(10_000);
} catch (InterruptedException e) {
e.printStackTrace();
}

System.out.println("predicate: before containsKey");
boolean b1 = cache1.containsKey(node.id().toString());

System.out.println("predicate: returning");
return b1;
});

System.out.println("Deploying service with cache-based predicate");
new Thread(() -> {
ignite1.services(group).deployNodeSingleton("testService", new 
TestService());
}).start();
System.out.println("Service in deployment.");

latch.await();

System.out.println("Starting second Ignite instance..");
Ignite ignite2 = 
Ignition.start(igniteConfiguration.setGridName("grid2"));
System.out.println("Second Ignite instance started successfully!"); // 
This isn't going to be printed.
}

public static class TestService implements Service
{
public void execute(ServiceContext ctx) throws Exception { 
System.out.println("execute()"); }
public void init(ServiceContext ctx) throws Exception { 
System.out.println("init()"); }
public void cancel(ServiceContext ctx) { 
System.out.println("cancel()"); }
}
}

{code}

Output:
{noformat}
[16:27:01]__   
[16:27:01]   /  _/ ___/ |/ /  _/_  __/ __/ 
[16:27:01]  _/ // (7 7// /  / / / _/   
[16:27:01] /___/\___/_/|_/___/ /_/ /___/  
[16:27:01] 
[16:27:01] ver. 1.5.0-b1#20151201-sha1:062d440c
[16:27:01] 2015 Copyright(C) Apache Software Foundation
[16:27:01] 
[16:27:01] Ignite documentation: http://ignite.apache.org
[16:27:01] 
[16:27:01] Quiet mode.
[16:27:01]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[16:27:01] 
[16:27:01] OS: Mac OS X 10.11 x86_64
[16:27:01] VM information: Java(TM) SE Runtime Environment 1.8.0_66-b17 Oracle 
Corp

[jira] [Commented] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-2135:
---

I am able to reproduce this issue and I think it is due to lack of enough 
memory in the system. If number of nodes started = number of GB of RAM this 
issue is reproducible. 

Tested on a system with 4GB ram. 

output from node 1
[20:20:31] Topology snapshot [ver=20, servers=4, clients=0, CPUs=4, heap=3.9GB]
output from node 2
[20:20:31] Topology snapshot [ver=20, servers=4, clients=0, CPUs=4, heap=3.9GB]
output from node 3
[20:20:31] Topology snapshot [ver=20, servers=4, clients=0, CPUs=4, heap=3.9GB]

To fix the issue added a try /catch for CacheException.

output from node 4
>>> Cache continuous query example started.
Failed to run continuous query example.
[20:37:32] Ignite node stopped OK [uptime=00:00:03:584]


> ClassNotFoundException for CacheContinuousQueryExample
> --
>
> Key: IGNITE-2135
> URL: https://issues.apache.org/jira/browse/IGNITE-2135
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 1.6
>
>
> 1. Start 3 nodes with examples/config/example-ignite.xml
> 2. Run CacheContinuousQueryExample in IDEA
> 3. The example fails:
> {noformat}
> >>> Cache continuous query example started.
> [14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Query execution failed: 
> GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
>   at 
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
>   at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>   at 
> org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 9 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088

[jira] [Commented] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-2135:
---

I have raised a PR for this issue.

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

> ClassNotFoundException for CacheContinuousQueryExample
> --
>
> Key: IGNITE-2135
> URL: https://issues.apache.org/jira/browse/IGNITE-2135
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 1.6
>
>
> 1. Start 3 nodes with examples/config/example-ignite.xml
> 2. Run CacheContinuousQueryExample in IDEA
> 3. The example fails:
> {noformat}
> >>> Cache continuous query example started.
> [14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Query execution failed: 
> GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
>   at 
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
>   at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>   at 
> org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 9 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null], 
> nodeId=a17e9748-7771-441c-a594-122c598b7b8e]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:390)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:395)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:60)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributed

[jira] [Commented] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-2135:
---

Please assign this ticket to me.

> ClassNotFoundException for CacheContinuousQueryExample
> --
>
> Key: IGNITE-2135
> URL: https://issues.apache.org/jira/browse/IGNITE-2135
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 1.6
>
>
> 1. Start 3 nodes with examples/config/example-ignite.xml
> 2. Run CacheContinuousQueryExample in IDEA
> 3. The example fails:
> {noformat}
> >>> Cache continuous query example started.
> [14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Query execution failed: 
> GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
>   at 
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
>   at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>   at 
> org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 9 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null], 
> nodeId=a17e9748-7771-441c-a594-122c598b7b8e]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:390)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:395)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:60)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQuer

[jira] [Assigned] (IGNITE-2004) Asynchronous execution of ContinuousQuery's remote filter

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko reassigned IGNITE-2004:
---

Assignee: Valentin Kulichenko

> Asynchronous execution of ContinuousQuery's remote filter
> -
>
> Key: IGNITE-2004
> URL: https://issues.apache.org/jira/browse/IGNITE-2004
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Valentin Kulichenko
> Fix For: 1.6
>
>
> Presently remote filters are executed synchronously an entry update. This 
> leads to the limitation when it's disallowed to perform cache related 
> operation in a filter body.
> It's required to add the ability to execute remote filters asynchronously. 
> This will let to execute any kind of operations including cache operations 
> directly in the filter body.
> The solution must be fault-tolerant. At least once execution of a filter in 
> case of a failure works fine. 



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

[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-1371:


I haven't looked into the patch yet, but is embedded Cassandra test is the only 
way to test new functionality? Because if there are other test coverage in 
there, embedding Cassandra could be done as a separate ticket. 

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Updated] (IGNITE-2143) inner join produce wrong result and is very slow

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated IGNITE-2143:
---
Description: 
I have following query for gitarchive records processing.  
{code}
select 
 lang, count(distinct ForkTable.repo_url) as cnt 
from (
 select repo_url, lang from gitrecord where type = 'ForkEvent' and 
 lang is not null group by lang, repo_url) as ForkTable 
inner join (
 select repo_url, html_url from gitrecord where type='PullRequestEvent'
 group by repo_url, html_url) as PullTable 
on 
 ForkTable.repo_url = PullTable.repo_url 
group by lang 
order by cnt desc
{code}

And there are two major problems:
1. It produces an incorrect result if it's running in cluster mode.
2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
Spark for the same query

Steps to reproduce:
1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
{code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
3. run ignite with attached config.xml 
4. run spark-shell
{code}
spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
/usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
spark://{spark-master}:7077
{code}
5. load data and execute the query:
{code}
import org.apache.ignite._
import org.apache.ignite.configuration._
import org.apache.ignite.cache.query._
import org.apache.ignite.spark._
import org.apache.ignite.lang.IgniteBiPredicate
import io.dtk._
val df = sqlContext.read.json("/Data/*.gz")
Ignition.setClientMode(true)
val cacheName = "gitrecords"

val rdd = df.select("id", "repo.url", 
"payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
 => (row.getString(0), new GitRecord(0, 
row.getString(1),row.getString(2),row.getString(3),row.getString(4

val cfg = new 
CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
val ic = new IgniteContext[String,GitRecord](sc, 
"/usr/lib/ignite-hadoop/config/config.xml")
val sharedRDD = ic.fromCache(cfg)
sharedRDD.savePairs(rdd)
sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
(select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is not 
null group by lang, repo_url) as ForkTable inner join (select repo_url, 
html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by lang 
order by cnt desc").show
{code}



  was:
I have following query for gitarchive records processing.  
{code}
select 
 lang, count(distinct ForkTable.repo_url) as cnt 
from (
 select repo_url, lang from gitrecord where type = 'ForkEvent' and 
 lang is not null group by lang, repo_url) as ForkTable 
inner join (
 select repo_url, html_url from gitrecord where type='PullRequestEvent'
 group by repo_url, html_url) as PullTable 
on 
 ForkTable.repo_url = PullTable.repo_url 
group by lang 
order by cnt desc
{code}

And there are two major problems:
1. It produces an incorrect result if it's running in cluster mode.
2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
Spark for the same query

Steps to reproduce:
1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz
2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
3. run ignite with attached config.xml 
4. run spark-shell
{code}
spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
/usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
spark://{spark-master}:7077
{code}
5. load data and execute the query:
{code}
import org.apache.ignite._
import org.apache.ignite.configuration._
import org.apache.ignite.cache.query._
import org.apache.ignite.spark._
import org.apache.ignite.lang.IgniteBiPredicate
import io.dtk._
val df = sqlContext.read.json("/Data/*.gz")
Ignition.setClientMode(true)
val cacheName = "gitrecords"

val rdd = df.select("id", "repo.url", 
"payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
 => (row.getString(0), new GitRecord(0, 
row.getString(1),row.getString(2),row.getString(3),row.getString(4

val cfg = new 
CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
val ic = new IgniteContext[String,GitRecord](sc, 
"/usr/lib/ignite-hadoop/config/config.xml")
val sharedRDD = ic.fromCache(cfg)
sharedRDD.savePairs(rdd)
sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as 

[jira] [Commented] (IGNITE-2143) inner join produce wrong result and is very slow

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-2143:


I wonder if this is a performance (and code) regression?

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



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

[jira] [Assigned] (IGNITE-435) Visor should use smart format for time values

[YoungGyu Chun (JIRA)]

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

YoungGyu Chun reassigned IGNITE-435:


Assignee: YoungGyu Chun

> Visor should use smart format for time values
> -
>
> Key: IGNITE-435
> URL: https://issues.apache.org/jira/browse/IGNITE-435
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: YoungGyu Chun
>Priority: Minor
>
> {code}
>  Maximum job execute time| 60009ms  - should show 1m
>  Curent job execute time | 120ms
>  Average job execute time| 1126.57ms - should show 1s
>  Total busy time | 70769ms - should show 1m 10s
> {code}
> Also please fix the typo 'Curent' - should be 'Current'



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

[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak commented on IGNITE-1371:
-

As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as connection points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Comment Edited] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak edited comment on IGNITE-1371 at 12/13/15 11:46 PM:


As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- [b]org/apache/ignite/tests/cassandra/connection.properties[b] - here you 
should specify Cassandra nodes which will be used as connection points to 
connect to Cassandra cluster (you can just randomly specify several nodes from 
your cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.


was (Author: irudyak):
As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as connection points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Comment Edited] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak edited comment on IGNITE-1371 at 12/13/15 11:45 PM:


As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as connection points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.


was (Author: irudyak):
As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as connection points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Comment Edited] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak edited comment on IGNITE-1371 at 12/13/15 11:46 PM:


As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as contact points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.


was (Author: irudyak):
As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as connection points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Comment Edited] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Igor Rudyak (JIRA)]

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

Igor Rudyak edited comment on IGNITE-1371 at 12/13/15 11:46 PM:


As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- org/apache/ignite/tests/cassandra/connection.properties - here you should 
specify Cassandra nodes which will be used as connection points to connect to 
Cassandra cluster (you can just randomly specify several nodes from your 
cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.


was (Author: irudyak):
As for now, to execute unit tests you should have real Cassandra cluster (not 
embedded). To run unit/load tests against the cluster you just need to modify 
such test resources:

- [b]org/apache/ignite/tests/cassandra/connection.properties[b] - here you 
should specify Cassandra nodes which will be used as connection points to 
connect to Cassandra cluster (you can just randomly specify several nodes from 
your cluster).

- org/apache/ignite/tests/cassandra/credentials.properties - here you should 
specify login/password to connect to Cassandra cluster.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Closed] (IGNITE-1856) Cache statements and plan info for SQL queries.

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin closed IGNITE-1856.
--

> Cache statements and plan info for SQL queries.
> ---
>
> Key: IGNITE-1856
> URL: https://issues.apache.org/jira/browse/IGNITE-1856
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergi Vladykin
>Assignee: Sergi Vladykin
> Fix For: 1.5
>
>




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

[jira] [Resolved] (IGNITE-1856) Cache statements and plan info for SQL queries.

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin resolved IGNITE-1856.

Resolution: Fixed

> Cache statements and plan info for SQL queries.
> ---
>
> Key: IGNITE-1856
> URL: https://issues.apache.org/jira/browse/IGNITE-1856
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergi Vladykin
>Assignee: Sergi Vladykin
> Fix For: 1.5
>
>




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

[jira] [Updated] (IGNITE-878) Large GC if load data to the cache using datastreamer

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-878:
--
Fix Version/s: (was: 1.5)
   1.6

> Large GC if load data to the cache using datastreamer 
> --
>
> Key: IGNITE-878
> URL: https://issues.apache.org/jira/browse/IGNITE-878
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
> Fix For: 1.6
>
> Attachments: #_IGNITE-878_GC_using_on_data_streaming_test.patch, 
> ig-878.png
>
>




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

[jira] [Updated] (IGNITE-735) Need to add support for dynamic indexes

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-735:
--
Fix Version/s: (was: 1.5)
   1.6

> Need to add support for dynamic indexes
> ---
>
> Key: IGNITE-735
> URL: https://issues.apache.org/jira/browse/IGNITE-735
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Alexey Kuznetsov
>Assignee: Sergi Vladykin
> Fix For: 1.6
>
>
> We should support indexes for any data type, including Map, Collection, or 
> complex object.



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

[jira] [Updated] (IGNITE-1495) Cache SQL query metadata index's fields have wrong register.

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-1495:
---
Fix Version/s: (was: 1.5)
   1.6

> Cache SQL query metadata index's fields have wrong register.
> 
>
> Key: IGNITE-1495
> URL: https://issues.apache.org/jira/browse/IGNITE-1495
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Sergi Vladykin
> Fix For: 1.6
>
> Attachments: #_IGNITE-1495_Test_for_index_s_fields.patch
>
>
> Index's fields should have register how in table fields (In upper case).



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

[jira] [Updated] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-1338:
---
Fix Version/s: (was: 1.5)
   1.6

> SQL engine doesn't convert query fields name in upper case before using
> ---
>
> Key: IGNITE-1338
> URL: https://issues.apache.org/jira/browse/IGNITE-1338
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Trivial
> Fix For: 1.6
>
> Attachments: test-cluster-2.xml
>
>
> Node can not be started if query fields name written in *lower case* and key 
> fields with the *same* fields in *upper case* in cache type metadata.
> Please use attached configuration file for reproducing.
> {code}
> [14:30:28,526][SEVERE][main][IgniteKernal] Got exception while starting (will 
> rollback startup routine).
> class org.apache.ignite.IgniteCheckedException: Failed to register query 
> type: TypeDescriptor [name=org.apache.ignite.Comalgorithm, 
> fields={APCSBJCODE=class java.math.BigDecimal, APCID=class 
> java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class 
> java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class 
> java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class 
> java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class 
> java.math.BigDecimal, algcode=class java.math.BigDecimal, 
> algisversioned=class java.lang.Short, algtype=class java.lang.Integer, 
> algcalcobjecttype=class java.lang.Integer, algclasspath=class 
> java.lang.String, algcomment=class java.lang.String, algopendate=class 
> java.sql.Date, algclosedate=class java.sql.Date, algentstatus=class 
> java.lang.Integer, agrsbjcode=class java.math.BigDecimal, agrid=class 
> java.math.BigDecimal, daosbjcode=class java.math.BigDecimal, daoid=class 
> java.math.BigDecimal, ctpsbjcode=class java.math.BigDecimal, ctpid=class 
> java.math.BigDecimal, algusefields=class java.lang.String}, 
> indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED], 
> FK3COMALGORITHM=IndexDescriptor [type=SORTED], 
> FK4COMALGORITHM=IndexDescriptor [type=SORTED], 
> SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null, 
> keyCls=class java.lang.Object, valCls=class java.lang.Object, 
> valTextIdx=false, registered=false]
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1058)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:194)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:292)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1048)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:820)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:963)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
>   at 
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546)
>   at org.apache.ignite.Ignition.start(Ignition.java:346)
>   at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
> Duplicate column name "APCSBJCODE"; SQL statement:
> CREATE TABLE "cache2".org_apache_ignite_Comalgorithm (_key OTHER NOT 
> NULL,_val OTHER,APCSBJCODE DECIMAL,APCID DECIMAL,AGRSBJCODE DECIMAL,AGRID 
> DECIMAL,DAOSBJCODE DECIMAL,DAOID DECIMAL,CTPSBJCODE DECIMAL,CTPID 
> DECIMAL,apcsbjcode DECIMAL,apcid DECIMAL,algcode DECIMAL,algisversioned 
> SMALLINT,algtype INT,algcalcobjecttype INT,algclasspath VARCHAR,algcomment 
> VARCHAR,algopendate DATE,algclosedate DATE,algentstatus INT,agrsbjcode 
> DECIMAL,agrid DECIMAL,daosbjcode DECIMAL,daoid DECIMAL,ctpsbjcode 
> DECIMAL,ctpid DECIMAL,algusefields VARCHAR) engine 
> "org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine" 
> [42121-175]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java

[jira] [Updated] (IGNITE-1886) NPE in H2 when running query with subselects

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-1886:
---
Fix Version/s: (was: 1.5)
   1.6

> NPE in H2 when running query with subselects
> 
>
> Key: IGNITE-1886
> URL: https://issues.apache.org/jira/browse/IGNITE-1886
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Sergi Vladykin
>Priority: Critical
> Fix For: 1.6
>
> Attachments: QueryTest.java
>
>
> Test reproducing the issue is attached. NPE is thrown as a result (see below).
> Corresponding user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Does-Ignite-support-nested-SQL-Queries-td1714.html
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Failed to parse query: SELECT a.* FROM 
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:636)
>   at 
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query: 
> SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:641)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:627)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> query: SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END 
> id FROM "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT 
> CASE WHEN og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1510)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:634)
>   ... 7 more
> Caused by: javax.cache.CacheException: Failed to parse query: SELECT a.* FROM 
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:938)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:636)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:634)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   ... 8 more
> Caused by: org.h2.jdbc.JdbcSQLException: General error: 
> "java.lang.NullPointerException" [5-175]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
>   at org.h2.message.DbException.get(DbException.java:161)
>   at org.h2.message.DbException.convert(DbException.java:284)
>   at org.h2.message.DbException.toSQLException(DbException.java:257)
>   at org.h2.message.TraceObject.logAndConvert(TraceObject.java:368)
>   at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:270)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:935)
>   ... 12 more
> Caused by: java.lang.NullPointerException
>   at org.h2.expression.Function.

[jira] [Updated] (IGNITE-1577) IlligateStateException when removing index during stop

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-1577:
---
Fix Version/s: (was: 1.5)
   1.6

> IlligateStateException when removing index during stop
> --
>
> Key: IGNITE-1577
> URL: https://issues.apache.org/jira/browse/IGNITE-1577
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Dmitriy Setrakyan
>Assignee: Sergi Vladykin
>Priority: Critical
> Fix For: 1.6
>
>
> I ran string example which queries the streamed words onto 2 data nodes (2GB 
> each, started with ExampleNodeStartup class), and while running, killed 1 
> node. I also had 1 StreamWords and 1 QueryWords process.
> Got this error on the stopping node.
> {code}
> java.lang.IllegalStateException: Failed to remove from index (grid is 
> stopping).
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:837)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:433)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clearIndex(GridCacheMapEntry.java:3553)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:3374)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$CleanupWorker.body(GridCacheTtlManager.java:136)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Updated] (IGNITE-969) Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non String value (Integer in my case)

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin updated IGNITE-969:
--
Fix Version/s: (was: 1.5)
   1.6

> Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non 
> String value (Integer in my case)
> --
>
> Key: IGNITE-969
> URL: https://issues.apache.org/jira/browse/IGNITE-969
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: 1.6
>
>
> {code}
> 
> 
> 
>  value="org.gridgain.visor.tester.sql.AddressKey"/>
>  value="org.gridgain.visor.tester.sql.Address"/>
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.VARCHAR"/>
> 
> 
>  value="java.lang.String"/>
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> zip
> street
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
>  

[jira] [Resolved] (IGNITE-2125) Refactoring popup more-info on configuration pages

[Dmitriyff (JIRA)]

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

Dmitriyff resolved IGNITE-2125.
---
Resolution: Fixed
  Assignee: Andrey Novikov  (was: Dmitriyff)

> Refactoring popup more-info on configuration pages
> --
>
> Key: IGNITE-2125
> URL: https://issues.apache.org/jira/browse/IGNITE-2125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriyff
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[jira] [Assigned] (IGNITE-2144) [Test] IgniteSemaphore's failover related tests are failing to compile

[Saikat Maitra (JIRA)]

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

Saikat Maitra reassigned IGNITE-2144:
-

Assignee: Saikat Maitra

> [Test] IgniteSemaphore's failover related tests are failing to compile
> --
>
> Key: IGNITE-2144
> URL: https://issues.apache.org/jira/browse/IGNITE-2144
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Minor
>
> GridCacheAbstractDataStructuresFailoverSelfTest are failing to compile.
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile 
> (default-testCompile) on project ignite-core: Compilation failure: 
> Compilation failure:
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[458,25]
>  constructor ConstantTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[465,25]
>  constructor ConstantTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.ConstantTopologyChangeWorker
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[472,25]
>  method multipleTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] 
> /Users/saikat/git/ignite/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheAbstractDataStructuresFailoverSelfTest.java:[479,25]
>  method multipleTopologyChangeWorker in class 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest
>  cannot be applied to given types;
> [ERROR] required: int
> [ERROR] found: no arguments
> [ERROR] reason: actual and formal argument lists differ in length



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

[jira] [Assigned] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Saikat Maitra (JIRA)]

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

Saikat Maitra reassigned IGNITE-2135:
-

Assignee: Saikat Maitra

> ClassNotFoundException for CacheContinuousQueryExample
> --
>
> Key: IGNITE-2135
> URL: https://issues.apache.org/jira/browse/IGNITE-2135
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>Priority: Critical
> Fix For: 1.6
>
>
> 1. Start 3 nodes with examples/config/example-ignite.xml
> 2. Run CacheContinuousQueryExample in IDEA
> 3. The example fails:
> {noformat}
> >>> Cache continuous query example started.
> [14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Query execution failed: 
> GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
>   at 
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
>   at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>   at 
> org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 9 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null], 
> nodeId=a17e9748-7771-441c-a594-122c598b7b8e]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:390)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:395)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:60)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:90)
>

[jira] [Created] (IGNITE-2147) Fix show content on summary page after navigation

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2147:
-

 Summary: Fix show content on summary page after navigation 
 Key: IGNITE-2147
 URL: https://issues.apache.org/jira/browse/IGNITE-2147
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff






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

[jira] [Closed] (IGNITE-2125) Refactoring popup more-info on configuration pages

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-2125.
--
Assignee: (was: Andrey Novikov)

Reviewed, merged.

> Refactoring popup more-info on configuration pages
> --
>
> Key: IGNITE-2125
> URL: https://issues.apache.org/jira/browse/IGNITE-2125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriyff
> Fix For: 1.6
>
>




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

[jira] [Updated] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2030:
---
Assignee: Semen Boikov  (was: Sergey Kozlov)

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Commented] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2030:


I'm noticed that when I'm starting visor I got such error in visor's console:
{code}
"!convertArgsCmd!" не является внутренней или внешней
командой, исполняемой программой или пакетным файлом.
{code}

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Comment Edited] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-2030 at 12/14/15 4:29 AM:
--

I'm noticed that when I'm starting visor (on Windows) I got such error in 
visor's console:
{code}
"!convertArgsCmd!" не является внутренней или внешней
командой, исполняемой программой или пакетным файлом.
{code}


was (Author: pkonstantinov):
I'm noticed that when I'm starting visor I got such error in visor's console:
{code}
"!convertArgsCmd!" не является внутренней или внешней
командой, исполняемой программой или пакетным файлом.
{code}

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Closed] (IGNITE-1932) Wrong value of BusyTimePercentage metric after ignite.cluster().resetMetrics()

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Wrong value of BusyTimePercentage metric after ignite.cluster().resetMetrics()
> --
>
> Key: IGNITE-1932
> URL: https://issues.apache.org/jira/browse/IGNITE-1932
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> I found that after call of
>   ignite.cluster().resetMetrics()
> BusyTimePercentage became 100% 
> After some debug I found that BusyTimePercentage - calculated as:
> 1 - IdleTimePercentage 
> and IdleTimePercentage  calculated as  IdleTime / UpTime
> and on reset we set IdleTime to 0.
> So the possible fix is to preserve IdleTime on reset.



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

[jira] [Created] (IGNITE-2148) Failed to start client node

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2148:


 Summary: Failed to start client node
 Key: IGNITE-2148
 URL: https://issues.apache.org/jira/browse/IGNITE-2148
 Project: Ignite
  Issue Type: Bug
  Components: clients
Affects Versions: 1.5
Reporter: Alexey Kuznetsov
Priority: Blocker
 Fix For: 1.5


I run code (this worked couple of days ago and also this code works with 
OptimizedMarshaller):

{code}
object TestScanNearCacheNodesLauncher extends App  {
def startServer(name: String): Ignite = {
val cfg = new IgniteConfiguration()

cfg.setGridName(name)

Ignition.start(cfg)
}

def startClientNode(name: String): Ignite = {
val cfg = new IgniteConfiguration()

cfg.setGridName(name)
cfg.setClientMode(true)

Ignition.start(cfg)
}

val sn1 = startServer("srv-1")
startServer("srv-2")
startServer("srv-3")

val srvCache1 = sn1.getOrCreateCache(new CacheConfiguration[String, 
String]("with-near"))
srvCache1.put("test_key1", "test_value1")
srvCache1.put("test_key2", "test_value2")
srvCache1.put("test_key3", "test_value3")
srvCache1.put("test_key4", "test_value4")

val srvCache2 = sn1.getOrCreateCache(new CacheConfiguration[String, 
String]("no-near"))
srvCache2.put("test_key5", "test_value5")
srvCache2.put("test_key6", "test_value6")

val cn1 = startClientNode("cln-1")
val cn2 = startClientNode("cln-2")
startClientNode("cln-3")

val nearCfg = new NearCacheConfiguration[String, String]
nearCfg.setNearEvictionPolicy(new FifoEvictionPolicy[String, String])

val nearCache1 = cn1.getOrCreateNearCache("with-near", nearCfg)
val nearCache2 = cn2.getOrCreateNearCache("with-near", nearCfg)

println("Value from near cache on cln-1: " + nearCache1.get("test_key1"))
println("Value from near cache on cln-1: " + nearCache1.get("test_key2"))
println("Value from near cache on cln-2: " + nearCache2.get("test_key3"))

println("Type 'q' and press 'Enter' to exit...")

while ('q' != System.in.read()) {
// No-op.
}

Ignition.stopAll(true)

System.exit(0)
}
{code}

I got:
{code}
Exception in thread "main" java.lang.AssertionError: BinaryMetadataKey 
[typeId=1877955432]
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1806)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.localPeek(GridCacheAdapter.java:727)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localPeek(IgniteCacheProxy.java:739)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:486)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:196)
at 
org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:562)
at 
org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:517)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:418)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.marshal(BinaryMarshaller.java:95)
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:965)
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:938)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryRequest.prepareMarshal(GridCacheQueryRequest.java:287)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:620)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.safeSend(GridCacheIoManager.java:697)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.sendRequest(GridCacheDistributedQueryManager.java:748)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.queryDistributed(GridCacheDistributedQueryManager.java:587)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.execute(GridCacheQueryAdapter.java:477)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.execute(GridCacheQueryAdapter.java:400)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onUtilityCacheStarted(CacheObjectB

[jira] [Reopened] (IGNITE-2093) Add support for scan near cache to VisorQueryTask

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reopened IGNITE-2093:

  Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

Please add support for scan of near cache in visorcmd
# add new option scan-near
# ask user for a node (if not provided in -n option)

> Add support for scan near cache to VisorQueryTask
> -
>
> Key: IGNITE-2093
> URL: https://issues.apache.org/jira/browse/IGNITE-2093
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.5
>
>
> VisorQueryTask can execute EXPLAIN, SQL and SCAN queries, but it is not so 
> hard add support for SCAN NEAR CACHE "pseudo query" that will work on some 
> node locally and will return 
> ccache.localEntries(CachePeekMode.NEAR).iterator().



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

[jira] [Updated] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2030:
---
Priority: Critical  (was: Major)

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Assigned] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-2030:


Assignee: Vladimir Ershov  (was: Semen Boikov)

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Resolved] (IGNITE-2145) Async cache operations on primary node might block

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko resolved IGNITE-2145.
-
Resolution: Won't Fix

{{EntryProcessor}} has to be invoked atomically, regardless of whether you're 
executing it synchronously or asynchronously. This means that the entry will be 
locked during the execution.

If you need to execute a long-running task collocated with the data, you can 
use {{IgniteCompute.affinityRun()}} method instead, which sends a closure to 
the node where the entry is stored without locking it.

> Async cache operations on primary node might block
> --
>
> Key: IGNITE-2145
> URL: https://issues.apache.org/jira/browse/IGNITE-2145
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Windows 8.1 64 bit
> java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>
> When executing async operations on caches the initial function call is 
> supposed to return immediately, without regard to cache state, network 
> traffic, etc. If we reference a cache key on a different node it works. But 
> if the primary node for a cache key is the same node that initiate the 
> operation everything is executed synchronously.
> This is probably an optimization, but can have side effects. For example, if 
> a long running CacheProcessor is invoked on this key, every operation will 
> block.
> Here is some code to illustrate the problem. Notice that there is a 4 seconds 
> delay between "Before async op" and "After async op". If you reverse the 
> isPrimary() condition it won't happen.
> {code}
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration()
>   .setFailoverSpi(new AlwaysFailoverSpi())
>   .setGridLogger(new Slf4jLogger())
>   .setPeerClassLoadingEnabled(false)
>   .setDeploymentMode(DeploymentMode.CONTINUOUS);
> Ignite ignite1 = Ignition.start(igniteConfiguration);
> Ignite ignite2 = Ignition.start(igniteConfiguration.setGridName("2"));
> assert ignite1.cluster().nodes().size() == 2;
> assert ignite2.cluster().nodes().size() == 2;
> CacheConfiguration cacheConfiguration = new 
> CacheConfiguration()
>   .setName("test")
>   .setCacheMode(CacheMode.PARTITIONED)
>   .setAtomicityMode(CacheAtomicityMode.ATOMIC)
>   
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> IgniteCache cache1 = 
> ignite1.getOrCreateCache(cacheConfiguration);
> IgniteCache cache2 = 
> ignite2.getOrCreateCache(cacheConfiguration);
> // Find key mapped to the first node
> String key = IntStream.range(0, 100)
>   .mapToObj(value -> "HI" + value)
>   .filter(s -> 
> ignite1.affinity(cacheConfiguration.getName()).isPrimary(ignite1.cluster().localNode(),
>  s))
>   .findFirst().get();
> // Run a blocked processor from node 2
> Thread thread = new Thread() {
>   @Override
>   public void run() {
>   System.out.println("Invoking blocked processor");
>   cache2.invoke(key, (entry, arguments) -> {
>   System.out.println("IN INVOKE");
>   try {
>   Thread.sleep(5 * 1000);
>   } catch (InterruptedException e) {
>   e.printStackTrace();
>   }
>   return null;
>   });
>   System.out.println("Blocked invoke returned");
>   }
> };
> thread.start();
> Thread.sleep(1000);
> IgniteCache async1 = cache1.withAsync();
> System.out.println("Before async op");
> //async1.put(key, 1);
> //async1.get(key);
> async1.containsKey(key);
> System.out.println("After async op");
> assert async1.future().isDone();
> thread.join();
> ignite2.close();
> ignite1.close();
> {code}



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

[jira] [Created] (IGNITE-2149) Build Apache Ignite failed for Java8

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2149:
-

 Summary: Build Apache Ignite failed for Java8
 Key: IGNITE-2149
 URL: https://issues.apache.org/jira/browse/IGNITE-2149
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Artem Shutak
Priority: Blocker
 Fix For: 1.5


{noformat}
[19:20:12] : [exec] [WARNING] 
COMPILATION WARNING : 
[19:20:12] : [exec] [INFO] 
-
[19:20:12] : [exec] [WARNING] 
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
 Some input files use unchecked or unsafe operations.
[19:20:12] : [exec] [WARNING] 
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
 Recompile with -Xlint:unchecked for details.
[19:20:12] : [exec] [INFO] 2 
warnings 
[19:20:12] : [exec] [INFO] 
-
[19:20:12] : [exec] [INFO] 
-
[19:20:12] : [exec] [ERROR] 
COMPILATION ERROR : 
[19:20:12] : [exec] [INFO] 
-
[19:20:12] : [exec] [ERROR] 
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteBinaryObjectFieldsQuerySelfTest.java:[213,17]
 reference to assertEquals is ambiguous
[19:20:12] : [exec]   both method 
assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase and 
method assertEquals(int,int) in junit.framework.TestCase match
[19:20:12] : [exec] [INFO] 1 error
[19:20:12] : [exec] [INFO] 
-
[19:20:12] : [exec] [INFO] 

[19:20:12] : [exec] [INFO] Reactor 
Summary:
[19:20:12] : [exec] [INFO] 
[19:20:12] : [exec] [INFO] 
ignite-apache-license-gen . SUCCESS [1.177s]
[19:20:12] : [exec] [INFO] 
ignite-tools .. SUCCESS [6.047s]
[19:20:12] : [exec] [INFO] 
ignite-core ... SUCCESS [1:11.104s]
[19:20:12] : [exec] [INFO] 
ignite-log4j .. SUCCESS [1.929s]
[19:20:12] : [exec] [INFO] 
ignite-urideploy .. SUCCESS [2.380s]
[19:20:12] : [exec] [INFO] 
ignite-spring . SUCCESS [2.634s]
[19:20:12] : [exec] [INFO] 
ignite-hadoop . SUCCESS [5.968s]
[19:20:12] : [exec] [INFO] 
ignite-extdata-p2p  SUCCESS [2.085s]
[19:20:12] : [exec] [INFO] 
ignite-extdata-uri-dep  SUCCESS [1.272s]
[19:20:12] : [exec] [INFO] 
ignite-extdata-uri  SUCCESS [0.388s]
[19:20:12] : [exec] [INFO] 
ignite-indexing ... FAILURE [1.375s]
[19:20:12] : [exec] [INFO] 
ignite-rest-http .. SKIPPED
[19:20:12] : [exec] [INFO] 
ignite-clients  SKIPPED
[19:20:12] : [exec] [INFO] 
ignite-web  SKIPPED
[19:20:12] : [exec] [INFO] 
ignite-aop  SKIPPED
[19:20:

[jira] [Commented] (IGNITE-2148) Failed to start client node

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2148:
-

Project re-build resolves the problem.

> Failed to start client node
> ---
>
> Key: IGNITE-2148
> URL: https://issues.apache.org/jira/browse/IGNITE-2148
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 1.5
>
>
> I run code (this worked couple of days ago and also this code works with 
> OptimizedMarshaller):
> {code}
> object TestScanNearCacheNodesLauncher extends App  {
> def startServer(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> Ignition.start(cfg)
> }
> def startClientNode(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> cfg.setClientMode(true)
> Ignition.start(cfg)
> }
> val sn1 = startServer("srv-1")
> startServer("srv-2")
> startServer("srv-3")
> val srvCache1 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("with-near"))
> srvCache1.put("test_key1", "test_value1")
> srvCache1.put("test_key2", "test_value2")
> srvCache1.put("test_key3", "test_value3")
> srvCache1.put("test_key4", "test_value4")
> val srvCache2 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("no-near"))
> srvCache2.put("test_key5", "test_value5")
> srvCache2.put("test_key6", "test_value6")
> val cn1 = startClientNode("cln-1")
> val cn2 = startClientNode("cln-2")
> startClientNode("cln-3")
> val nearCfg = new NearCacheConfiguration[String, String]
> nearCfg.setNearEvictionPolicy(new FifoEvictionPolicy[String, String])
> val nearCache1 = cn1.getOrCreateNearCache("with-near", nearCfg)
> val nearCache2 = cn2.getOrCreateNearCache("with-near", nearCfg)
> println("Value from near cache on cln-1: " + nearCache1.get("test_key1"))
> println("Value from near cache on cln-1: " + nearCache1.get("test_key2"))
> println("Value from near cache on cln-2: " + nearCache2.get("test_key3"))
> println("Type 'q' and press 'Enter' to exit...")
> while ('q' != System.in.read()) {
> // No-op.
> }
> Ignition.stopAll(true)
> System.exit(0)
> }
> {code}
> I got:
> {code}
> Exception in thread "main" java.lang.AssertionError: BinaryMetadataKey 
> [typeId=1877955432]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localPeek(GridCacheAdapter.java:727)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localPeek(IgniteCacheProxy.java:739)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:486)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:196)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:562)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:517)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:418)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal(BinaryMarshaller.java:95)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:965)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:938)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryRequest.prepareMarshal(GridCacheQueryRequest.java:287)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:620)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.safeSend(GridCacheIoManager.java:697)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.sendRequest(GridCacheDistributedQueryManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.queryDistributed(GridCacheDistributedQueryManager.java:587)
>   at 

[jira] [Assigned] (IGNITE-2148) Failed to start client node

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-2148:


Assignee: Alexey Kuznetsov

> Failed to start client node
> ---
>
> Key: IGNITE-2148
> URL: https://issues.apache.org/jira/browse/IGNITE-2148
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 1.5
>
>
> I run code (this worked couple of days ago and also this code works with 
> OptimizedMarshaller):
> {code}
> object TestScanNearCacheNodesLauncher extends App  {
> def startServer(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> Ignition.start(cfg)
> }
> def startClientNode(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> cfg.setClientMode(true)
> Ignition.start(cfg)
> }
> val sn1 = startServer("srv-1")
> startServer("srv-2")
> startServer("srv-3")
> val srvCache1 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("with-near"))
> srvCache1.put("test_key1", "test_value1")
> srvCache1.put("test_key2", "test_value2")
> srvCache1.put("test_key3", "test_value3")
> srvCache1.put("test_key4", "test_value4")
> val srvCache2 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("no-near"))
> srvCache2.put("test_key5", "test_value5")
> srvCache2.put("test_key6", "test_value6")
> val cn1 = startClientNode("cln-1")
> val cn2 = startClientNode("cln-2")
> startClientNode("cln-3")
> val nearCfg = new NearCacheConfiguration[String, String]
> nearCfg.setNearEvictionPolicy(new FifoEvictionPolicy[String, String])
> val nearCache1 = cn1.getOrCreateNearCache("with-near", nearCfg)
> val nearCache2 = cn2.getOrCreateNearCache("with-near", nearCfg)
> println("Value from near cache on cln-1: " + nearCache1.get("test_key1"))
> println("Value from near cache on cln-1: " + nearCache1.get("test_key2"))
> println("Value from near cache on cln-2: " + nearCache2.get("test_key3"))
> println("Type 'q' and press 'Enter' to exit...")
> while ('q' != System.in.read()) {
> // No-op.
> }
> Ignition.stopAll(true)
> System.exit(0)
> }
> {code}
> I got:
> {code}
> Exception in thread "main" java.lang.AssertionError: BinaryMetadataKey 
> [typeId=1877955432]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localPeek(GridCacheAdapter.java:727)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localPeek(IgniteCacheProxy.java:739)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:486)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:196)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:562)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:517)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:418)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal(BinaryMarshaller.java:95)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:965)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:938)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryRequest.prepareMarshal(GridCacheQueryRequest.java:287)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:620)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.safeSend(GridCacheIoManager.java:697)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.sendRequest(GridCacheDistributedQueryManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.queryDistributed(GridCacheDistributedQueryManager.java:587)
>   at 
> org.apache.igni

[jira] [Commented] (IGNITE-2143) inner join produce wrong result and is very slow

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin commented on IGNITE-2143:


Guys,

The result is wrong because GROUP BY is only supported at the top level query, 
we can't use it in sub-queries now (we will improve that in future releases).

I'd suggest to use a flat query like
```
select 
 ForkTable.lang, count(distinct ForkTable.repo_url) as cnt 
from 
 gitrecord ForkTable, gitrecord PullTable
where 
  ForkTable.repo_url = PullTable.repo_url  
  and ForkTable.type = 'ForkEvent'
  and PullTable.type='PullRequestEvent'
  and ForkTable.lang is not null
group by lang 
order by cnt desc
```
and create index on (type, repo_url)

Also you have to make sure that GitRecord.repo_url is an affinity key.

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



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

[jira] [Comment Edited] (IGNITE-2143) inner join produce wrong result and is very slow

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin edited comment on IGNITE-2143 at 12/14/15 7:29 AM:
--

Guys,

The result is wrong because GROUP BY is only supported at the top level query, 
we can't use it in sub-queries now (we will improve that in future releases).

I'd suggest to use a flat query like
{code}
select 
 ForkTable.lang, count(distinct ForkTable.repo_url) as cnt 
from 
 gitrecord ForkTable, gitrecord PullTable
where 
  ForkTable.repo_url = PullTable.repo_url  
  and ForkTable.type = 'ForkEvent'
  and PullTable.type='PullRequestEvent'
  and ForkTable.lang is not null
group by lang 
order by cnt desc
{code}
and create index on (type, repo_url)

Also you have to make sure that GitRecord.repo_url is an affinity key.


was (Author: sergi.vladykin):
Guys,

The result is wrong because GROUP BY is only supported at the top level query, 
we can't use it in sub-queries now (we will improve that in future releases).

I'd suggest to use a flat query like
```
select 
 ForkTable.lang, count(distinct ForkTable.repo_url) as cnt 
from 
 gitrecord ForkTable, gitrecord PullTable
where 
  ForkTable.repo_url = PullTable.repo_url  
  and ForkTable.type = 'ForkEvent'
  and PullTable.type='PullRequestEvent'
  and ForkTable.lang is not null
group by lang 
order by cnt desc
```
and create index on (type, repo_url)

Also you have to make sure that GitRecord.repo_url is an affinity key.

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



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

[jira] [Resolved] (IGNITE-2148) Failed to start client node

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2148.
--
Resolution: Not A Problem

mvn clean package -DskipTests -DskipClientDocs -Dmaven.javadoc.skip=true

Solved this issue.

> Failed to start client node
> ---
>
> Key: IGNITE-2148
> URL: https://issues.apache.org/jira/browse/IGNITE-2148
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 1.5
>
>
> I run code (this worked couple of days ago and also this code works with 
> OptimizedMarshaller):
> {code}
> object TestScanNearCacheNodesLauncher extends App  {
> def startServer(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> Ignition.start(cfg)
> }
> def startClientNode(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> cfg.setClientMode(true)
> Ignition.start(cfg)
> }
> val sn1 = startServer("srv-1")
> startServer("srv-2")
> startServer("srv-3")
> val srvCache1 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("with-near"))
> srvCache1.put("test_key1", "test_value1")
> srvCache1.put("test_key2", "test_value2")
> srvCache1.put("test_key3", "test_value3")
> srvCache1.put("test_key4", "test_value4")
> val srvCache2 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("no-near"))
> srvCache2.put("test_key5", "test_value5")
> srvCache2.put("test_key6", "test_value6")
> val cn1 = startClientNode("cln-1")
> val cn2 = startClientNode("cln-2")
> startClientNode("cln-3")
> val nearCfg = new NearCacheConfiguration[String, String]
> nearCfg.setNearEvictionPolicy(new FifoEvictionPolicy[String, String])
> val nearCache1 = cn1.getOrCreateNearCache("with-near", nearCfg)
> val nearCache2 = cn2.getOrCreateNearCache("with-near", nearCfg)
> println("Value from near cache on cln-1: " + nearCache1.get("test_key1"))
> println("Value from near cache on cln-1: " + nearCache1.get("test_key2"))
> println("Value from near cache on cln-2: " + nearCache2.get("test_key3"))
> println("Type 'q' and press 'Enter' to exit...")
> while ('q' != System.in.read()) {
> // No-op.
> }
> Ignition.stopAll(true)
> System.exit(0)
> }
> {code}
> I got:
> {code}
> Exception in thread "main" java.lang.AssertionError: BinaryMetadataKey 
> [typeId=1877955432]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localPeek(GridCacheAdapter.java:727)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localPeek(IgniteCacheProxy.java:739)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:486)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:196)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:562)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:517)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:418)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal(BinaryMarshaller.java:95)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:965)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:938)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryRequest.prepareMarshal(GridCacheQueryRequest.java:287)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:620)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.safeSend(GridCacheIoManager.java:697)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.sendRequest(GridCacheDistributedQueryManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.q

[jira] [Closed] (IGNITE-2148) Failed to start client node

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-2148.

Assignee: (was: Alexey Kuznetsov)

> Failed to start client node
> ---
>
> Key: IGNITE-2148
> URL: https://issues.apache.org/jira/browse/IGNITE-2148
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 1.5
>
>
> I run code (this worked couple of days ago and also this code works with 
> OptimizedMarshaller):
> {code}
> object TestScanNearCacheNodesLauncher extends App  {
> def startServer(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> Ignition.start(cfg)
> }
> def startClientNode(name: String): Ignite = {
> val cfg = new IgniteConfiguration()
> cfg.setGridName(name)
> cfg.setClientMode(true)
> Ignition.start(cfg)
> }
> val sn1 = startServer("srv-1")
> startServer("srv-2")
> startServer("srv-3")
> val srvCache1 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("with-near"))
> srvCache1.put("test_key1", "test_value1")
> srvCache1.put("test_key2", "test_value2")
> srvCache1.put("test_key3", "test_value3")
> srvCache1.put("test_key4", "test_value4")
> val srvCache2 = sn1.getOrCreateCache(new CacheConfiguration[String, 
> String]("no-near"))
> srvCache2.put("test_key5", "test_value5")
> srvCache2.put("test_key6", "test_value6")
> val cn1 = startClientNode("cln-1")
> val cn2 = startClientNode("cln-2")
> startClientNode("cln-3")
> val nearCfg = new NearCacheConfiguration[String, String]
> nearCfg.setNearEvictionPolicy(new FifoEvictionPolicy[String, String])
> val nearCache1 = cn1.getOrCreateNearCache("with-near", nearCfg)
> val nearCache2 = cn2.getOrCreateNearCache("with-near", nearCfg)
> println("Value from near cache on cln-1: " + nearCache1.get("test_key1"))
> println("Value from near cache on cln-1: " + nearCache1.get("test_key2"))
> println("Value from near cache on cln-2: " + nearCache2.get("test_key3"))
> println("Type 'q' and press 'Enter' to exit...")
> while ('q' != System.in.read()) {
> // No-op.
> }
> Ignition.stopAll(true)
> System.exit(0)
> }
> {code}
> I got:
> {code}
> Exception in thread "main" java.lang.AssertionError: BinaryMetadataKey 
> [typeId=1877955432]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localPeek(GridCacheAdapter.java:727)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localPeek(IgniteCacheProxy.java:739)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:486)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.addMeta(CacheObjectBinaryProcessorImpl.java:196)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:562)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:517)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:418)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal(BinaryMarshaller.java:95)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:965)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.marshal(GridCacheUtils.java:938)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryRequest.prepareMarshal(GridCacheQueryRequest.java:287)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:620)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.safeSend(GridCacheIoManager.java:697)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.sendRequest(GridCacheDistributedQueryManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.queryDistributed(GridCacheDistributedQueryManager.java:587)
>   at 
> org.apache.ignite.internal.processors.cache.query.Gri

[jira] [Created] (IGNITE-2150) BinaryMarshallerSelfTest fails on TC.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2150:
---

 Summary: BinaryMarshallerSelfTest fails on TC.
 Key: IGNITE-2150
 URL: https://issues.apache.org/jira/browse/IGNITE-2150
 Project: Ignite
  Issue Type: Bug
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.5


Link: 
http://ci.ignite.apache.org/viewLog.html?buildId=86125&tab=buildResultsDiv&buildTypeId=IgniteTests_IgniteBinaryObjectsBasic

Reason is unknow.



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

[jira] [Closed] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: 111-configuration.zip
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Created] (IGNITE-2151) 'secret.properties' generated with empty body

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2151:
--

 Summary: 'secret.properties' generated with empty body
 Key: IGNITE-2151
 URL: https://issues.apache.org/jira/browse/IGNITE-2151
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko






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

[jira] [Commented] (IGNITE-2150) BinaryMarshallerSelfTest fails on TC.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2150:
--

Seems Alexey G. already investigated this issue.

> BinaryMarshallerSelfTest fails on TC.
> -
>
> Key: IGNITE-2150
> URL: https://issues.apache.org/jira/browse/IGNITE-2150
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Link: 
> http://ci.ignite.apache.org/viewLog.html?buildId=86125&tab=buildResultsDiv&buildTypeId=IgniteTests_IgniteBinaryObjectsBasic
> Reason is unknow.



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

[jira] [Updated] (IGNITE-2093) Add support for scan near cache to VisorQueryTask

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2093:
-
Fix Version/s: (was: 1.5)
   1.6

> Add support for scan near cache to VisorQueryTask
> -
>
> Key: IGNITE-2093
> URL: https://issues.apache.org/jira/browse/IGNITE-2093
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.6
>
>
> VisorQueryTask can execute EXPLAIN, SQL and SCAN queries, but it is not so 
> hard add support for SCAN NEAR CACHE "pseudo query" that will work on some 
> node locally and will return 
> ccache.localEntries(CachePeekMode.NEAR).iterator().



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