Re: Cassandra and Ignite C++ Issue

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: >

Reason for disabling @QuerySqlField and @AffinityKeyMapped annotations on methods

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

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

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

Cassandra and Ignite C++ Issue

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

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

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

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

Persistent Store example fails with NPE

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

Persistent Store configuration is renamed

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

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

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

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

> 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 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

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

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

Re: ignite-pds and binary objects

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

ignite-pds and binary objects

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

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

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

[GitHub] ignite pull request #1958: Ignite 5052

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

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

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

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

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 г. в

H2PkHashIndex

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...

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