Re: Cassandra and Ignite C++ Issue

[Igor Rudyak]

I assume that's because you are using this:




Current implementation supports only BLOB serialization for binary objects.
We already have a ticket for this:
https://issues.apache.org/jira/browse/IGNITE-5270

Igor



On Thu, May 25, 2017 at 8:19 PM, Denis Magda  wrote:

> Igor R., Igor S.,
>
> Please take a look at this issue reported on SO:
> https://stackoverflow.com/questions/44178514/ignite-c-
> client-for-cassandra-integration
>
> --
> Denis
>

Reason for disabling @QuerySqlField and @AffinityKeyMapped annotations on methods

[Igor Rudyak]

Hi guys,

Does anybody know what's the reason for disabling *@QuerySqlField* and
*@AffinityKeyMapped* annotations on methods in *Ignite 2.1* ?

Just found two JIRA tickets for this, but there are no details there:

https://issues.apache.org/jira/browse/IGNITE-5036
https://issues.apache.org/jira/browse/IGNITE-4950

The problem is that this implementation brakes backward compatibility for
previous deployments utilizing Ignite-Cassandra module and POJO classes
using such annotations.

Igor

[jira] [Created] (IGNITE-5296) Web console: Wrong queries list on clear of cookies

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-5296:
-

 Summary: Web console: Wrong queries list on clear of cookies
 Key: IGNITE-5296
 URL: https://issues.apache.org/jira/browse/IGNITE-5296
 Project: Ignite
  Issue Type: Bug
Reporter: Vasiliy Sisko


# Create some queries lists.
# Clear all cookies
# Refresh page and login.

After login list of queries showed as empty. It is sowed after refresh.



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

Cassandra and Ignite C++ Issue

[Denis Magda]

Igor R., Igor S.,

Please take a look at this issue reported on SO:
https://stackoverflow.com/questions/44178514/ignite-c-client-for-cassandra-integration

--
Denis

Re: [VOTE] Accept Contribution of Ignite Persistent Store

[Denis Magda]

Folks,

The IP clearance vote has passed:
http://apache-incubator-general.996316.n3.nabble.com/RESULT-IP-CLEARANCE-Apache-Ignite-Persistent-Store-td55050.html

Raul, please see below:

> On May 24, 2017, at 12:18 PM, Raúl Kripalani  wrote:
> 
>> 
>> Raul, I think everyone got confused on the process. At this point, the code
>> has not been merged to master, and is sitting in a separate branch. I would
>> recommend that we proceed with the vote. If the vote is declined, then we
>> will toss the branch.
> 
> 
> Just for the record. I don't want to complicate matters further, but IIRC,
> the instant the code starts living in the ASF repo (which it already does),
> it forms part of the project's codebase. And that means that the PMC and
> the committers are responsible for it.
> 
> Hence the vote to accept responsibility on something that the PMC is
> already responsible for, is somewhat questionable.
> 
> On the other hand, the IP clearance indicates what's being donated is the
> tree of a particular commit from an external repo [0]. But it seems that
> work was done after that commit in the external branch. Is it possible that
> the code that was merged was different than that specific commit? Not sure
> if this is relevant, as long as all files have the ASF license grant
> header, but now is the time to ensure correct due diligence. Better to
> ask…
> 

A pretty similar question (extra merges after that specified commit) was raised 
during the IP clearance vote:
http://apache-incubator-general.996316.n3.nabble.com/IP-CLEARANCE-Apache-Ignite-Persistent-Store-td54969.html

However, since now we have all the changes in a single branch 
(https://github.com/apache/ignite/tree/ignite-5267 
) and can see the changes 
set comparing to the master 
(https://github.com/apache/ignite/compare/ignite-5267 
) it shouldn’t be longer 
an issue. At least this resolved concerns on the IP clearance vote.

—
Denis
 
> Cos, or anybody?
> 
> [0]
> https://github.com/agoncharuk/ignite/commit/1cce2fcc960c5098cc684b6138ed306daf5dd5e4
> 
> 
> Raúl.
> 
> On Tue, May 23, 2017 at 5:04 PM, Dmitriy Setrakyan 
> wrote:
> 
>> +1
>> 
>> Raul, I think everyone got confused on the process. At this point, the code
>> has not been merged to master, and is sitting in a separate branch. I would
>> recommend that we proceed with the vote. If the vote is declined, then we
>> will toss the branch.
>> 
>> I believe that once this feature is fully released, which will make Apache
>> Ignite into an SQL database and In-Memory data grid at the same time, the
>> community and user base of Apache Ignite will get a healthy boost.
>> 
>> D.
>> 
>> On Tue, May 23, 2017 at 2:53 AM, Raúl Kripalani 
>> wrote:
>> 
>>> I'm not sure what the vote is for, if the code has already been merged to
>>> the ASF repo — even if on a branch.
>>> 
>>> I do accept the donation but I think the code should have remained
>> outside
>>> the official codebase until the VOTE passed.
>>> 
>>> Not sure what the rest think.
>>> 
>>> On 22 May 2017 22:55, "Denis Magda"  wrote:
>>> 
 Igniters,
 
 This branch (https://github.com/apache/ignite/tree/ignite-5267) adds a
 distributed and transactional Persistent Store to Apache Ignite
>> project.
 The store seamlessly integrates with Apache Ignite 2.0 page memory
 architecture. One of the main advantages of the store is that Apache
>>> Ignite
 becomes fully operational from disk (SSD or Flash) without any need to
 preload the data in memory. Plus, with full SQL support already
>> available
 in Apache Ignite, this feature will allow Apache Ignite serve as a
 distributed SQL database, both in memory or on disk, while continuing
>> to
 support all the existing functionality on the current API.
 More information here:
 - Persistent Store Overview: https://cwiki.apache.org/
 confluence/display/IGNITE/Persistent+Store+Overview
 - Persistent Store Internal Design: https://cwiki.apache.org/
 confluence/display/IGNITE/Persistent+Store+Internal+Design
 The Persistent Store was developed by GridGain outside of Apache
>>> community
 because it was requested by one of GridGain’s customers. Presently,
 GridGain looks forward to donating the Persistent Store to ASF and
>> given
 the size of the contribution, it is prudent to follow Apache's IP
>>> clearance
 process.
 The SGA has been submitted and acknowledged by ASF Secretary. The IP
 clearance form can be found here: http://incubator.apache.org/
 ip-clearance/persistent-distributed-store-ignite.html
 This vote is to discover if the Apache Ignite PMC and community are in
 favour of accepting this contribution.
 This vote will be open for at least 72 hours:
 [ ] +1, accept contribution of the Persistent Store 

[jira] [Created] (IGNITE-5295) NPE when Persistent Store is used and Memory Configuration is missing

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5295:
---

 Summary: NPE when Persistent Store is used and Memory 
Configuration is missing
 Key: IGNITE-5295
 URL: https://issues.apache.org/jira/browse/IGNITE-5295
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Alexey Goncharuk
Priority: Blocker
 Fix For: 2.1


Just added the first Persistent Store example to the branch that fosters the 
donation:
https://github.com/apache/ignite/tree/ignite-5267/examples/src/main/java/org/apache/ignite/examples/persistentstore

However, the example fails with an NPE if a MemoryConfiguration is not defined 
explicitly.

{code}
[17:55:39,334][ERROR][main][IgniteKernal] Exception during start processors, 
node will be stopped and close connections
class org.apache.ignite.IgniteCheckedException: Failed to start processor: 
GridProcessorAdapter []
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1766)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:925)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:993)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:879)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:648)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:617)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at 
org.apache.ignite.examples.persistentstore.PersistentStoreExample.main(PersistentStoreExample.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
Ignite component (consider adding ignite-pds module to classpath) 
[component=DATABASE_MANAGER, 
cls=org.apache.ignite.internal.processors.cache.database.GridCacheDatabaseSharedManager]
at 
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:335)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:311)
at 
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:186)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createSharedContext(GridCacheProcessor.java:2078)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:632)
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
... 16 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:307)
... 20 more
Caused by: java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.database.GridCacheDatabaseSharedManager.(GridCacheDatabaseSharedManager.java:284)
... 25 more
[17:55:39,338][ERROR][main][IgniteKernal] Got exception while starting (will 
rollback startup routine).
class org.apache.ignite.IgniteCheckedException: Failed to start processor: 
GridProcessorAdapter []
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1766)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:925)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:993)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:879)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
at 

Persistent Store example fails with NPE

[Denis Magda]

Igniters,

I’ve just added the first Persistent Store example to the branch that fosters 
the donation:
https://github.com/apache/ignite/tree/ignite-5267/examples/src/main/java/org/apache/ignite/examples/persistentstore

However, the example fails with an NPE if a MemoryConfiguration is not defined 
explicitly:
https://issues.apache.org/jira/browse/IGNITE-5295

Please those who are involved in the store development fix the issue by the end 
of tomorrow. I want to complete with the technical documentation referring to a 
workable example.

—
Denis

Persistent Store configuration is renamed

[Denis Magda]

Folks, FYI

In order to align the naming of the store from marketing, documentation levels 
to the APIs level, PersistenceConfiguration was renamed to 
PersistentStoreConfiguration.

The changes are merged to this branch: 
https://github.com/apache/ignite/tree/ignite-5267 


—
Denis

[jira] [Created] (IGNITE-5294) Document Persistent Store

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5294:
---

 Summary: Document Persistent Store
 Key: IGNITE-5294
 URL: https://issues.apache.org/jira/browse/IGNITE-5294
 Project: Ignite
  Issue Type: Sub-task
Reporter: Denis Magda
Assignee: Denis Magda


Document the Persistent Store. Use these wiki pages as reference:
https://cwiki.apache.org/confluence/display/IGNITE/Persistent+Store+Overview
https://cwiki.apache.org/confluence/display/IGNITE/Persistent+Store+Internal+Design



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

Re: IgfsPerBlockLruEvictionPolicy does not work as expected any more, what shall we do with it?

[Denis Magda]

> On May 25, 2017, at 5:17 AM, Ivan V.  wrote:
> 
> I think, we should answer the following questions.
> 1) does the interface org.apache.ignite.cache.eviction.EvictionPolicy and
> *all* its implementations now de-facto get deprecated? (I mean, the
> question appears to be wider than just the IGFS eviction policy).

Now, this interface is used for “on-heap caching” scenario:
https://apacheignite.readme.io/docs/page-memory#on-heap-caching

Here is we clarify what this interfaced is used for:
https://apacheignite.readme.io/docs/evictions#on-heap-cache-entries-based-eviction

> 2) is on-heap data access faster than off-heap? If yes, how large the
> on-heap vs. off-heap difference is?

It’s comparable. Hope the guys can share precise numbers.

In general, the on-heap caching is for scenarios when you do a lot of cache 
reads on server nodes that work with cache entries in the binary form or invoke 
cache entries' deserialization. For instance, this might happen when a 
distributed computation or deployed service gets some data from caches for 
further processing.

> 3) does an ability to evict from on-heap layer make any sense at all if the
> same data are anyway backed up by off-heap cache layer, that has different
> eviction policies?

As soon as you enable the on-heap caching you should set up a eviction policy. 
Otherwise the Java heap can grow endlessly.

—
Denis

> 
> 
> On Thu, May 25, 2017 at 2:42 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
> 
>> Guys, I think it makes little or no sense to keep blocks on-heap. If I
>> understand correctly, the eviction policy was used in combined modes where
>> partial data eviction is allowed. To make this work in the new PageMemory
>> architecture, we only need to make sure that IGFS block size equals to the
>> data page free space size. In this case, our standard offheap eviction
>> policy will be semantically equal to the old per-block eviction policy. No
>> need to go on-heap at all.
>> 
>> Thoughts?
>> 
>> 2017-05-25 4:21 GMT+03:00 Denis Magda :
>> 
>>> Hi Ivan,
>>> 
>>> I’m for this approach
>>> 
 2) leave it as is, but explain in javadocs that it only works for
>> on-heap
 layer, that does not in fact evict  blocks from the underlying offheap
 layer.
>>> 
>>> because it should be feasible to enable on-heap caching for IGFS, right?
>>> Using the memory policies. So, I would reimplement the tests with the
>>> on-heap caching enabling and checking up that data is pushed out of the
>>> heap.
>>> 
>>> —
>>> Denis
>>> 
 On May 24, 2017, at 9:57 AM, Ivan V. 
>> wrote:
 
 Hi, colleagues,
 
 as Ignite caches moved to paged offheap memory , the
 IgfsPerBlockLruEvictionPolicy does not seem to work as expected any
>> more,
 because
 1) interface org.apache.ignite.cache.eviction.EvictionPolicy now only
 defines "eviction from on-heap", not a real eviction, because each
>>> on-heap
 cache is now accompanied with underlying off-heap cache. It can become
 "real eviction" only for "on-heap-only" mode caches, once they get
 implemented.
 2) for off-heap eviction an entire page is evicted, not a specific k-v
 pair, and LRU policy is not exactly LRU any more (see
 org.apache.ignite.configuration.DataPageEvictionMode#RANDOM_LRU). So,
>> it
 appears to be impossible to re-implement this policy for the off-heap
>>> layer.
 
 Thus, now IgfsPerBlockLruEvictionPolicy is not quite valid, and some of
 corresponding tests fail
 (org.apache.ignite.internal.processors.igfs.
>>> IgfsCachePerBlockLruEvictionPolicySelfTest#testDataSizeEviction,
 org.apache.ignite.internal.processors.igfs.
>>> IgfsCachePerBlockLruEvictionPolicySelfTest#testBlockCountEviction)
 
 So, the options I see are:
 1) deprecate/remove IgfsPerBlockLruEvictionPolicy ;
 2) leave it as is, but explain in javadocs that it only works for
>> on-heap
 layer, that does not in fact evict  blocks from the underlying offheap
 layer.
 
 Please share your opinions.
>>> 
>>> 
>> 

[jira] [Created] (IGNITE-5293) Replicated cache performance degradation.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-5293:
-

 Summary: Replicated cache performance degradation.
 Key: IGNITE-5293
 URL: https://issues.apache.org/jira/browse/IGNITE-5293
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Alexei Scherbakov


With increase in number of nodes puts to replicated cache are slowed down 
almost in the same proportion.

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

package org.apache.ignite.internal.processors.cache.distributed.replicated;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheWriteSynchronizationMode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.MemoryConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;

/**
 * Tests replicated cache performance .
 */
public class GridCacheReplicatedTransactionalDegradationTest extends 
GridCommonAbstractTest {
/** Keys. */
private static final int KEYS = 100_000;

@Override protected IgniteConfiguration getConfiguration(String gridName) 
throws Exception {
IgniteConfiguration cfg = super.getConfiguration(gridName);

cfg.setClientMode(gridName.startsWith("client"));

CacheConfiguration ccfg = new CacheConfiguration();

ccfg.setCacheMode(CacheMode.REPLICATED);
ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);

ccfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
ccfg.setName("test");

cfg.setCacheConfiguration(ccfg);

return cfg;
}

/** */
public void testThroughput() throws Exception {
try {
IgniteEx grid0 = startGrid(0);

Ignite client = startGrid("client");

IgniteCache cache = client.getOrCreateCache("test");

doTest(client, cache);

startGrid(1);

doTest(client, cache);

startGrid(2);

doTest(client, cache);
} finally {
stopAllGrids();
}
}

/**
 * @param client
 * @param cache Cache.
 */
private void doTest(Ignite client, IgniteCache cache) {
long t1 = System.currentTimeMillis();

for (int i = 0; i < KEYS; i++) {
try (Transaction tx = 
client.transactions().txStart(TransactionConcurrency.PESSIMISTIC, 
TransactionIsolation.REPEATABLE_READ)) {
cache.put(i, i);

tx.commit();
}
}

log.info("TPS: " + Math.round(KEYS / (float)(System.currentTimeMillis() 
- t1) * 1000));
}
}
{noformat}



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

[GitHub] ignite pull request #2010: Ignite-5290

[ntikhonov]

GitHub user ntikhonov opened a pull request:

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

Ignite-5290

Ignite-5290

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

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

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

https://github.com/apache/ignite/pull/2010.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2010


commit 4dd735ffa01966b400afba2403ed609f54117884
Author: vozerov-gridgain 
Date:   2016-10-24T08:33:41Z

Merge commit '60d27547' into ignite-1.7.3

commit 2c4c7a4b0539aac35f91e0e9cc61f2e74a088d83
Author: vozerov-gridgain 
Date:   2016-10-24T08:50:29Z

Merge commit '2ab094e0' into ignite-1.7.3

commit b9bb1f6bc02cb3054b1e9b9bfbd34b886db77624
Author: vozerov-gridgain 
Date:   2016-10-24T08:50:51Z

Merge commit '2ab094e0' into ignite-1.7.3.

commit bab33016dd7ba99e288f2eaed089a57f867f8af2
Author: Pavel Tupitsyn 
Date:   2016-10-24T09:12:33Z

merge eaf8ae24: IGNITE-4034 Get rid of specialized methods in platform 
targets

commit f97170b723e8ced39c7acae19fadb0039e7cafb7
Author: Pavel Tupitsyn 
Date:   2016-10-24T09:21:00Z

merge eaf8ae24: IGNITE-4034 Get rid of specialized methods in platform 
targets

commit e73125d96c2a8d1f5a53a5fc3d3ed58db1dc7713
Author: Pavel Tupitsyn 
Date:   2016-10-24T09:50:22Z

merge eaf8ae24: IGNITE-4034 Get rid of specialized methods in platform 
targets

commit 6d69701038eeefaff2291a909d63d85e1ab9a376
Author: Pavel Tupitsyn 
Date:   2016-10-24T10:44:47Z

Merge commit '46dc9fc1' into ignite-1.7.3 (IGNITE-4034 Get rid of 
specialized methods in platform targets)

commit 96243fbc410226002e98f15d73aeb96ecec23a2b
Author: Pavel Tupitsyn 
Date:   2016-10-24T10:53:21Z

.NET: Fix ComputeApiTestFullFooter.TestForDaemons

commit 7a2f9ab516e8bc855c04d6ae947de05837f485f7
Author: vozerov-gridgain 
Date:   2016-10-24T10:54:46Z

Merge commit '7adfbcf1' into ignite-1.7.3

commit 2eee94c1ce141d02a4877a1f501c99eb16b0930f
Author: vozerov-gridgain 
Date:   2016-10-24T10:55:49Z

Merge remote-tracking branch 'upstream/ignite-1.7.3' into ignite-1.7.3

commit 9fc3b5095b825b9ca00b45c18f8072f998dd2adf
Author: Pavel Tupitsyn 
Date:   2016-08-02T15:37:52Z

IGNITE-3497 .NET: Improve IgniteConfigurationSection.xsd: add missing 
properties, enums, docs.

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/IgniteConfigurationSerializerTest.cs

commit 04ac900a06b60fd58b7f5aa71c5371632fe03ede
Author: Pavel Tupitsyn 
Date:   2016-10-24T11:45:32Z

.NET: Fix TestCyrillicChars

commit f664751d2f5fda214ffa9df4f1375da4acd2f200
Author: isapego 
Date:   2016-10-24T11:50:50Z

Merge-related fix for C++.

commit 255b3a3e199b19757a511d4340f184a9de7afddc
Author: Pavel Tupitsyn 
Date:   2016-10-24T11:52:21Z

.NET: Fix ServicesTest.TestDuckTyping

commit ec12a9db2265180f96be72e2217e60ced856164e
Author: vozerov-gridgain 
Date:   2016-10-24T14:52:36Z

Minor fix for flags passed to GridCacheMapEntry.initialValue from data 
streamer isolated updater.

commit 02dd07a58277b357991c1f74a7dbdfdd9de2a2cc
Author: Pavel Tupitsyn 
Date:   2016-10-25T09:34:35Z

IGNITE-4074 Refactor async (*future) operations in PlatformTarget

commit 2a90fcaf8e46a829306ca92e226d984111b3aefe
Author: Pavel Tupitsyn 
Date:   2016-10-25T12:15:55Z

IGNITE-4028 .NET: Get rid of OP_META in PlatformAbstractTarget

commit bf266e971579cad0f40d233090c93f3acec06d0a
Author: vozerov-gridgain 
Date:   2016-10-17T08:26:12Z

IGNITE-4054: Hadoop: added map-reduce plan debug output.

commit 1e21d643aaf4d78e36fccaaeaa29cd3c49c90405
Author: sboikov 
Date:   2016-10-17T09:28:31Z

Fixed indexing test in according to changes from #80abd1b.

commit 51cef7c740828ffcc40f411a66e630421040a2d2
Author: Igor Sapego 
Date:   2016-10-18T08:53:46Z

IGNITE-4090: CPP: Fixed compilation for GCC 4.4.7. This closes #1165.

commit 442fedc17bdae43b1c87d6bb4680f724a18adb52
Author: vozerov-gridgain 
Date:   2016-10-18T09:25:56Z

Revert "IGNITE-3875: Added separate thread pool for data streamer. This 
closes #1067."

This reverts commit f597aff1bdf65d3d430cf85c9932391a72c2d7dc.

commit 46e77f912dfd741000c32aae03449df691d522b1
Author: tledkov-gridgain 
Date:   2016-10-18T10:01:03Z

IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest. 
Close FileSystem after 

[GitHub] ignite pull request #2009: IGNITE-4904 .NET: DML Delete via LINQ

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-4904 .NET: DML Delete via LINQ



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

$ git pull https://github.com/ptupitsyn/ignite ignite-4904

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

https://github.com/apache/ignite/pull/2009.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2009


commit 1c1ec13e28f91bd345f5262291e9c19d74fcdb3c
Author: Pavel Tupitsyn 
Date:   2017-05-22T15:26:17Z

IGNITE-4904 .NET: DML via LINQ

commit 9fab0e7b7945102e94012c352fbf6f7b21195793
Author: Pavel Tupitsyn 
Date:   2017-05-22T15:39:26Z

API and test added for DeleteAll

commit e044a9ea028b1299f33f5b47da9f1b3929e4c9dc
Author: Pavel Tupitsyn 
Date:   2017-05-22T15:41:40Z

wip

commit 00f6a6b9eaede6222db2cbd373a72af96be91460
Author: Pavel Tupitsyn 
Date:   2017-05-22T15:57:04Z

wip

commit 5af55be2fa778e88f9a725c361b06a673312324d
Author: Pavel Tupitsyn 
Date:   2017-05-22T16:20:02Z

wip adding ReLinq extensions

commit 73e29df8db06b42dfdc76e7378f0ff28eae64a33
Author: Pavel Tupitsyn 
Date:   2017-05-22T16:26:48Z

register new node in ReLinq

commit 9fd511e26fc03253cf7f7ae9e0786d44f3cafdf6
Author: Pavel Tupitsyn 
Date:   2017-05-22T16:39:39Z

wip

commit 896bf6e58663412bcce77f00f3d02aeb6b14a6ee
Author: Pavel Tupitsyn 
Date:   2017-05-22T16:49:35Z

wip fix extension

commit 042a4e48a482327ca86929c43526d657811acf00
Author: Pavel Tupitsyn 
Date:   2017-05-22T16:50:27Z

wip

commit 218a1decb79c364ca90c5b7289dffb5dde85e1ca
Author: Pavel Tupitsyn 
Date:   2017-05-22T16:54:40Z

Overload with predicate

commit 70c4e4c761b921b8b30ec4d0fe7d07be115daba9
Author: Pavel Tupitsyn 
Date:   2017-05-22T17:30:22Z

Add DeleteAll operator support to the engine

commit 3e897fe0684f47395affdcf084048f14d5abee27
Author: Pavel Tupitsyn 
Date:   2017-05-22T17:31:37Z

wip

commit 5f1c4046214aac0e7cdeee8404c1e0e86e892919
Author: Pavel Tupitsyn 
Date:   2017-05-22T17:33:51Z

Simple test works!

commit c76157c714b0fa6ec6824601c2053abb32f37799
Author: Pavel Tupitsyn 
Date:   2017-05-22T17:36:11Z

wip todos

commit ce5cd5fbc02a807410a456d4db0349cf60fe00ee
Author: Pavel Tupitsyn 
Date:   2017-05-23T12:36:57Z

Rename DeleteAll to RemoveAll

commit 496a832d46989c651da5f4b1db8fa06322753549
Author: Pavel Tupitsyn 
Date:   2017-05-23T13:02:56Z

wip

commit bcbd923fed2b1fd4ed6f1ec3710064d8724d7151
Author: Pavel Tupitsyn 
Date:   2017-05-23T13:04:05Z

wip RemoveAll with predicate

commit 69e49af97e7b5c2512228032f5e3c47706a6b667
Author: Pavel Tupitsyn 
Date:   2017-05-24T16:51:44Z

Merge branch 'master' into ignite-4904

commit c75d867293293be1fe275512cc6f82c27b951ae6
Author: Pavel Tupitsyn 
Date:   2017-05-24T16:57:30Z

tests with predicate

commit b070cc3c0d96568f9d6dfde55526fffc85464212
Author: Pavel Tupitsyn 
Date:   2017-05-24T17:04:49Z

add test with join

commit 64c7bc71e3aee9efabd309798cc90810e4ea471e
Author: Pavel Tupitsyn 
Date:   2017-05-24T17:08:23Z

wip todos

commit 4bbcfde8bad41d4982ecdeebbb26b6191051ab5d
Author: Pavel Tupitsyn 
Date:   2017-05-25T12:37:31Z

Merge branch 'master' into ignite-4904

commit ec8c0c908b79f88010f01ae3d0e4812685f118fe
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:22:36Z

wip

commit 765ba572bc0fa5445bcac02599146ac2433497c9
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:25:52Z

wip tests

commit f49b057f12586b8d27195573dd2453b1c1272ce6
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:35:28Z

wip

commit 42fa73cb648a6c92381a02f2c8764ef12240e76c
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:46:11Z

wip tests

commit 8d583a76694804ca0a239b1ac516ed7a5abac272
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:48:56Z

Tests done

commit 4c35a5c8c107bd7f42eb05647e36fc30370a7305
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:52:31Z

Tests done

commit 218c38843a738162e9cd60a5ccd358ea72b4d7ad
Author: Pavel Tupitsyn 
Date:   2017-05-25T14:56:09Z

add unconditional test

commit 5fd6efbfa5904c7a527463aeec2e347820f0d76f
Author: Pavel Tupitsyn 
Date:   2017-05-25T15:05:08Z

wip tests




---
If your project is set up for 

[GitHub] ignite pull request #1988: properties to configure memoryMetrics are added, ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2008: IGNITE-5291 Correct handling of cache stop in Ign...

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5291 Correct handling of cache stop in IgniteH2Indexing



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

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

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

https://github.com/apache/ignite/pull/2008.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2008


commit de522ebcc27807f4316b18349f5024f28f1bcf2b
Author: Alexander Paschenko 
Date:   2017-05-25T15:21:13Z

IGNITE-5291 Correct handling of cache stop in IgniteH2Indexing




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2007: gg-8.0.3.ea9

[agoncharuk]

GitHub user agoncharuk opened a pull request:

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

gg-8.0.3.ea9



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea9

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

https://github.com/apache/ignite/pull/2007.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2007


commit be881725b39926f62df437c2805ac9203fea5737
Author: Ilya Lantukh 
Date:   2016-10-11T16:19:20Z

gg-11595 : WIP.

commit e6d82d8da50b9af9607a914e00da3937d839862a
Author: Ilya Lantukh 
Date:   2016-10-12T16:20:50Z

gg-11595 : WIP.

commit cb9c18ccfc937b4a880eddb5df5d0389de9c7bee
Author: Ilya Lantukh 
Date:   2016-10-13T12:54:39Z

gg-11595 : WIP.

commit ed45f2238361e5bbbe907fdeb4b7a3d7b2b051dd
Author: Ilya Lantukh 
Date:   2016-10-27T13:02:28Z

gg-11595 : Support for restore with concurrent cache operations.

commit e95c68b77cbd3ad30d9f6d0b332137fb26000a41
Author: Ilya Lantukh 
Date:   2016-10-27T13:35:46Z

gg-11595 : Minors.

commit 7a44f1ebccf4fe0f26f54e070bbacbf24fbee3d7
Author: Ilya Lantukh 
Date:   2016-12-16T15:56:24Z

gg-11701 : WIP.

commit 3e2b28075ab5d00dce7fadf4769967f7a0ee2ee8
Author: Ilya Lantukh 
Date:   2016-12-19T12:25:11Z

Merge branches 'ignite-gg-11701' and 'ignite-gg-8.0.2.ea1' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11701

commit cc568f9f6823de04f0beeca45ada4160a58307e4
Author: Ilya Lantukh 
Date:   2016-12-21T13:11:36Z

gg-11701 : WIP

commit e93f8d43a92dd8bde12c4677b5fcc6b0c2de6ce6
Author: Ilya Lantukh 
Date:   2016-12-27T10:45:29Z

Merge branches 'ignite-gg-11701' and 'ignite-gg-8.0.2.ea1' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11701

commit 721f255eb2de1d8207e35328e2dec6514c22500d
Author: Ilya Lantukh 
Date:   2016-12-28T15:58:38Z

gg-11701 : Fixed preloading.

commit bed897dc01960dcbb7219ad948973e0f27bfa564
Author: Ilya Lantukh 
Date:   2016-12-28T16:31:51Z

gg-11701 : Fixed force keys request for single get.

commit 07535d92cd37cc949188434eb7ded2fc8d2e0647
Author: Ilya Lantukh 
Date:   2016-12-28T16:48:15Z

gg-11701 : Added check to multiple get.

commit ff9aa8898445c2a30e80fbc94f668eb5cd29a7d8
Author: Ilya Lantukh 
Date:   2016-12-29T13:04:49Z

Merge branches 'ignite-gg-11701' and 'ignite-gg-8.0.2.ea2' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11701

commit 6cbe8a5a8ea5e4dacb8c5a859cb15aea5b3f38af
Author: Ilya Lantukh 
Date:   2017-01-09T15:22:15Z

gg-11701 : Fixed partition update counters comparison.

commit 3c276c9e092b6f6b4baf0b550ad89cb85ab9c42f
Author: Ilya Lantukh 
Date:   2017-01-10T10:25:09Z

gg-11701 : Implicit lateAffinityAssignment mode when persistence is enabled.

commit b3f7ae3bf903a0a6357163029ed310647877c8fc
Author: Ilya Lantukh 
Date:   2017-01-10T11:25:24Z

gg-11701 : Replaced redundant checks with assertions.

commit 2e55ddb600819dbf4684c0e97cc71a733167a4ce
Author: Ilya Lantukh 
Date:   2017-01-11T15:05:25Z

gg-11701 : Merge with 8.0.2.ea2

commit ecead988090e6a65ffdbb4098252ea26287fe36e
Author: Ilya Lantukh 
Date:   2017-01-11T15:09:25Z

gg-11701 : Merge with 8.0.2.ea2

commit adc0422592a18a7c2635e45185ef17852cd41952
Author: Glukos 
Date:   2017-01-13T17:23:06Z

GG-11595:
Remote exception wrapped on proxy level

commit 4505066481d4fff601a14d344dc8059f5dbe73de
Author: Ivan Rakov 
Date:   2017-01-13T21:32:08Z

GG-11595:
+ serialVersionUid

commit ba847555c86c00a288362e1cfad8c4c30883975c
Author: Ivan Rakov 
Date:   2017-01-16T15:08:35Z

Merge branch 'ignite-gg-8.0.2.ea2#' into ignite-gg-11595

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/DynamicCacheChangeRequest.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheProcessor.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheProxy.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteDynamicCacheStartSelfTest.java

commit 9e6732822061319df1e934361cfaf96e06f91573
Author: 

[jira] [Created] (IGNITE-5291) SQL: plans cache does not clear on cache stop

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-5291:
---

 Summary: SQL: plans cache does not clear on cache stop
 Key: IGNITE-5291
 URL: https://issues.apache.org/jira/browse/IGNITE-5291
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.0
 Environment: After cache-schema decoupling mutation of 
{{DmlStatementsProcessor#planCache}} appears to be broken (different pieces of 
code contexts operate different schema names), have to do this consistently.
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.1






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

IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

[ALEKSEY KUZNETSOV]

Igntrs! Plz, review my changes
https://issues.apache.org/jira/browse/IGNITE-1094
*https://github.com/apache/ignite/pull/1904
* (preferrably review here)
http://reviews.ignite.apache.org/ignite/review/IGNT-CR-181

-- 

*Best Regards,*

*Kuznetsov Aleksey*

[jira] [Created] (IGNITE-5290) Events might be missed during concurrent CQ registration and cache operations

[Nikolay Tikhonov (JIRA)]

Nikolay Tikhonov created IGNITE-5290:


 Summary: Events might be missed during concurrent CQ registration 
and cache operations
 Key: IGNITE-5290
 URL: https://issues.apache.org/jira/browse/IGNITE-5290
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Nikolay Tikhonov


Events might be missed during concurrent CQ registration and cache operations. 
See attached test.



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

[GitHub] ignite pull request #2006: IGNITE-5288: Inconsistency of committed and the m...

[dspavlov]

GitHub user dspavlov opened a pull request:

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

IGNITE-5288: Inconsistency of committed and the max memory numbers …

…should not cause stopping cluster node

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

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

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

https://github.com/apache/ignite/pull/2006.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2006


commit 0fc8c4531a86a6f13a1387a0757d3ecbd5da1e36
Author: dpavlov 
Date:   2017-05-25T12:31:00Z

IGNITE-5288: Inconsistency of committed and the max memory numbers should 
not cause stopping cluster node




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: ignite-pds and binary objects

[Alexey Goncharuk]

Hi Igor,

The current implementation assumes that compactFooters should be disabled,
we did not enforce this configuration yet. However, generally, you are
right, and we must have a local-only metadata storage which will keep
binary metadata.

2017-05-25 14:46 GMT+03:00 Seliverstov Igor :

> Hi guys!
>
> Seems the new persistance feature is not compatable with our default
> configuration.
>
> A simplest test where I store an object type, restart the grid and try to
> get the object by its key fails with NPE:
>
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.
> CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl
> .java:492)
> at
> org.apache.ignite.internal.processors.cache.binary.
> CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl
> .java:174)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(
> BinaryContext.java:1231)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(
> BinaryReaderExImpl.java:1987)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.<
> init>(BinaryReaderExImpl.java:283)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.<
> init>(BinaryReaderExImpl.java:182)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.
> reader(BinaryObjectImpl.java:827)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(
> BinaryObjectImpl.java:791)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(
> BinaryObjectImpl.java:142)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.
> unwrapBinary(CacheObjectContext.java:273)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.
> unwrapBinaryIfNeeded(CacheObjectContext.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.
> unwrapBinaryIfNeeded(CacheObjectContext.java:148)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.
> unwrapBinaryIfNeeded(GridCacheContext.java:1713)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.
> GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture
> .java:648)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.
> GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture
> .java:441)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.
> GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture
> .java:327)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.
> GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture
> .java:212)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.
> GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture
> .java:204)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.atomic.GridDhtAtomicCache.getAsync0(GridDhtAtomicCache.java:1460)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.atomic.GridDhtAtomicCache.access$1600(GridDhtAtomicCache.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.atomic.GridDhtAtomicCache$16.apply(GridDhtAtomicCache.java:528)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.atomic.GridDhtAtomicCache$16.apply(GridDhtAtomicCache.java:526)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:821)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.atomic.GridDhtAtomicCache.getAsync(GridDhtAtomicCache.java:526)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(
> GridCacheAdapter.java:4458)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(
> GridCacheAdapter.java:4439)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(
> GridCacheAdapter.java:1326)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(
> IgniteCacheProxy.java:1180)
>
> Guess it happens because we don't store bynary metadata (with
> use-compact-footer=false everything works fine).
>
> Any thoughts on that?
>
> I suppose we have to store the binary metadata if the persistence is on.
>
> Regards,
> Igor
>

ignite-pds and binary objects

[Seliverstov Igor]

Hi guys!

Seems the new persistance feature is not compatable with our default
configuration.

A simplest test where I store an object type, restart the grid and try to
get the object by its key fails with NPE:

java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:492)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:174)
at
org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1231)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1987)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:283)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:182)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:827)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:791)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:273)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:161)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:148)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:648)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:441)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:327)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:212)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:204)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAsync0(GridDhtAtomicCache.java:1460)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1600(GridDhtAtomicCache.java:130)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$16.apply(GridDhtAtomicCache.java:528)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$16.apply(GridDhtAtomicCache.java:526)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:821)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAsync(GridDhtAtomicCache.java:526)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4458)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4439)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1326)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1180)

Guess it happens because we don't store bynary metadata (with
use-compact-footer=false everything works fine).

Any thoughts on that?

I suppose we have to store the binary metadata if the persistence is on.

Regards,
Igor

[GitHub] ignite pull request #2005: ignite-4496-1

[akuramshingg]

GitHub user akuramshingg opened a pull request:

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

ignite-4496-1

IGNITE-4496 Review all logging for sensitive data leak

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

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

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

https://github.com/apache/ignite/pull/2005.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2005


commit db02d5a0abb3b27d26f19b37daac0ad7d4cd7744
Author: Alexandr Kuramshin 
Date:   2017-05-25T11:05:40Z

IGNITE-4496 Review all logging for sensitive data leak

commit 281d5e8227fc360198d574211f6224db5d48a59d
Author: Alexandr Kuramshin 
Date:   2017-05-25T11:22:27Z

log.debug() fix
remove empty files




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1958: Ignite 5052

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2004: IGNITE-5287

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-5287



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

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

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

https://github.com/apache/ignite/pull/2004.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2004


commit 7dd23aa3f891659c5d455316b9bedda4c26d22b3
Author: devozerov 
Date:   2017-05-24T12:52:15Z

Started.

commit 7a7646d46080ec7e22476e744cd4b9973be066b6
Author: devozerov 
Date:   2017-05-24T15:26:11Z

Implemented normalization logic.

commit 3caf64a42bacf8cbe82d63797473949a521babbb
Author: devozerov 
Date:   2017-05-24T15:36:01Z

Minor fix. Normalization appears to be fine at this point.

commit c3773cc7de08ff31f70d9c77af55c9b53a55ce06
Author: devozerov 
Date:   2017-05-24T16:31:06Z

WIP.

commit 37a7c223f604680904d63743de7472ef86a85e6b
Author: devozerov 
Date:   2017-05-24T16:50:45Z

WIP.

commit cbcc8d4f58fdb0ec9d6b2c5a85b2c6330742be2f
Author: devozerov 
Date:   2017-05-25T07:38:17Z

WIP.

commit b48c8ff383bd9e174a31f04038f36f13ad0da0a3
Author: devozerov 
Date:   2017-05-25T07:50:24Z

List of failing tests.

commit f066b7748c3d749cebd2b1bd836f390328ab2462
Author: devozerov 
Date:   2017-05-25T07:55:14Z

Fixing tests.

commit 23f4f46b05929285ead36164d8a90f685c6dca93
Author: devozerov 
Date:   2017-05-25T08:06:24Z

WIP on tests.

commit 2195c14f8a203d9709b224ac68962ee8acf57a57
Author: devozerov 
Date:   2017-05-25T08:13:58Z

WIP on tests.

commit 8e438499f03ad450788a81d1c5d4fcbde9179b6d
Author: devozerov 
Date:   2017-05-25T08:48:37Z

Table name is always set.

commit 8227e6934f7690bf53bdb6925e03eb4a2f0dfcf3
Author: devozerov 
Date:   2017-05-25T09:19:10Z

WIP.

commit e790fa76899f974f67708a6f7ff45548260b953d
Author: devozerov 
Date:   2017-05-25T09:23:41Z

WIP.

commit 266e661f383604ae299125807658fd3f89420d8d
Author: devozerov 
Date:   2017-05-25T09:31:14Z

WIP.

commit 39d180fc7ec53b49a069b66d65ecc415a49a9ecc
Author: devozerov 
Date:   2017-05-25T10:11:35Z

Fixing tests.

commit b1aef1585e358a9c05ee4361cc7994d55de93299
Author: devozerov 
Date:   2017-05-25T10:12:23Z

Enabling tests.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: TC for master is moved to Ignite 2.0 test suite

[Dmitry Pavlov]

Hi Igniters,



'Ignite Binary Objects Basic' run configuration has been also removed from
'Ignite 2.0 Tests' chain.



Thanks Vladimir for pointing this out.



Please share ideas on what else can be optimized in the build/test process.



Best Regards,

Dmitriy Pavlov


вт, 23 мая 2017 г. в 14:54, Dmitry Pavlov :

> Hi Igniters,
>
>
> Please review PR with 'Binary Basic' merge into 'Basic'
> https://github.com/apache/ignite/pull/1991
>
>
> After PR is merged it will be possible to remove snapshot dependency from
> ‘Run All’ to  ‘Binary Basic’
>
> and remove run configuration.
>
> Best Regards,
>
> Dmitry Pavlov
>
> PS. TC run
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=625386=buildResultsDiv=Ignite20Tests_IgniteBinaryBasic
> (Without tests)
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=625387=buildResultsDiv=Ignite20Tests_IgniteBasic
>
>
> вт, 23 мая 2017 г. в 13:33, Dmitry Pavlov :
>
>> Yes, we can merge 'binary basic' into 'basic' with adding following tests
>> into 'basic':
>> o.a.i.internal.processors.cache.IgniteMarshallerCacheClassNameConflictTest
>> -testCachePutGetClassesWithNameConflict()
>>
>>
>> o.a.i.internal.processors.cache.IgniteMarshallerCacheClientRequestsMappingOnMissTest
>> -testAllNodesDieOnRequest()
>> -testNoNodesDieOnRequest()
>> -testOneNodeDiesOnRequest()
>> -testRequestedMappingIsStoredInFS()
>> -testTwoNodesDieOnRequest()
>>
>> it will save 37 minutes of agent time more. I'll prepare PR
>>
>> Best Regards,
>> Dmitry Pavlov
>>
>>
>> вт, 23 мая 2017 г. в 10:43, Vladimir Ozerov :
>>
>>> Pavel,
>>>
>>> Yes, these two:
>>>
>>> http://ci.ignite.apache.org/admin/editBuildParams.html?id=buildType:Ignite20Tests_IgniteBasic
>>>
>>> http://ci.ignite.apache.org/admin/editBuildParams.html?id=buildType:Ignite20Tests_IgniteBinaryBasic
>>>
>>> They both execute org.apache.ignite.testsuites.IgniteBasicTestSuite.
>>> Looks
>>> like we should merge them accurately.
>>>
>>> On Tue, May 23, 2017 at 10:27 AM, Dmitry Pavlov 
>>> wrote:
>>>
>>> > Hi, Vladimir,
>>> >
>>> > There is a chance that in
>>> > http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=
>>> > projectOverview
>>> > some
>>> > configs are for binary + simple oblect names (no package name) tests.
>>> >
>>> > But if there is some suspicious link that is candidate to removal,
>>> please
>>> > feel free to contact me.
>>> >
>>> > Best Regards,
>>> > Dmitry Pavlov
>>> >
>>> > вт, 23 мая 2017 г. в 10:24, Vladimir Ozerov :
>>> >
>>> > > Fantastic news, thank you guys! Though, I still see "Basic" and
>>> "Binary
>>> > > Object Basic" suites. Should we drop one of them as well?
>>> > >
>>> > > On Tue, May 23, 2017 at 10:20 AM, Alexey Goncharuk <
>>> > > alexey.goncha...@gmail.com> wrote:
>>> > >
>>> > > > Igniters,
>>> > > >
>>> > > > Since we removed OptimizedMarshaller in Ignite 2.0 from the
>>> PublicAPI,
>>> > we
>>> > > > had a chance to remove several unnecessary test suites from the
>>> build
>>> > > plan
>>> > > > from Ignite 2.0. I pushed the changes for IGNITE-4947 ticket. From
>>> this
>>> > > > moment you should run tests from Ignite 2.0 project, which is 14
>>> test
>>> > > > suites shorter than the previous plan.
>>> > > >
>>> > > > Kudos to Alexander Paschenko and Dmitriy Pavlov!
>>> > > >
>>> > > > --AG
>>> > > >
>>> > >
>>> >
>>>
>>

H2PkHashIndex

[Sergi Vladykin]

Guys,

Can someone explain why this strange thingy exists if it does not replace
usual PK tree index?

Sergi

[GitHub] ignite pull request #1991: Ignite-4947: Ignite Basic and Ignite Binary Basic...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---