Off-Heap SQL Indexes

Engineers, I was going through documentation for Off-Heap SQL Indexes and found two contradicting statements- According to [1] - " `CacheConfiguration.setOffHeapMaxMemory` is the only property to enable or disable off-heap

Re: Talking to Ignite From PHP

Igor, I can’t find branch ignite-3910. Most likely you keep the changes on the other one. Please double check. In any case, I succeeded with some of the steps from the documentation and updated it making clearer. http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability

Re: [DISCUSS] PMC Chair rotation time

While all the candidates suggested so far look good, I would propose Denis Magda as the next PMC chair. His participation in the project does not only have to do with the code, but also with Ignite project overall, including website, documentation, new tickets, design, etc. D. On Wed, Nov 2,

Re: [DISCUSS] PMC Chair rotation time

Just to reiterate the original premise for the rotation [1]: - it provides an opportunity to anyone in the PMC to try this hat on and get more involved in the inner-workings of the ASF and see how the board operates - it guarantees that once you're a chair you aren't stuck holding the bag forever

Re: Updating Ignite Version on Apache Camel Side

Perfect, thanks! — Denis > On Nov 2, 2016, at 10:46 AM, Raul Kripalani wrote: > > > Done. > > > > > > camel-ignite: Update Ignite to v1.7.0. · apache/camel@210502e >

Fwd: Updating Ignite Version on Apache Camel Side

Done. https://github.com/apache/camel/commit/210502e22bfa0eb313fcd57ace8baa4761122395 https://github.com/apache/camel/commit/210502e22bfa0eb313fcd57ace8baa4761122395 https://polymail.io/?utm_source=polymail_medium=referral_campaign=link-preview

Re: Apache Ignite 1.8 Release

Roman, Sure, it makes sense to include this into the release highlighting that presently Ignite provides a limited support. Please create a pull-request and send a message (not a part of this discussion) to the dev list asking for review. — Denis > On Nov 1, 2016, at 6:46 PM, Roman Shtykh

Fwd: Updating Ignite Version on Apache Camel Side

Sure, working on it! --- Raúl Kripalani http://linkedin.com/in/raulkripalani  |  http://evosent.com/?utm_source=email_medium=email_campaign=evosent_raul  | blog:  http://raul.io/?utm_source=email_medium=email_campaign=evosent_raul  | skype: raul.fuse On Wed 02 Nov 2016 at 17:27 Denis Magda <

Re: Updating Ignite Interpreter Guide on Zeppelin

Andrey, thanks a lot! — Denis > On Nov 2, 2016, at 10:24 AM, Andrey Gura wrote: > > Hi, all. > > I've update Ignite interpreter docs in Apache Zeppelin repository. PR: > https://github.com/apache/zeppelin/pull/1581 > > If you have some comments please notify. > > On Tue,

Re: Updating Ignite Interpreter Guide on Zeppelin

Hi, all. I've update Ignite interpreter docs in Apache Zeppelin repository. PR: https://github.com/apache/zeppelin/pull/1581 If you have some comments please notify. On Tue, Nov 1, 2016 at 4:08 PM, Andrey Gura wrote: > Hi, Denis. > > I'll try to fix this situation and notify

[GitHub] ignite pull request #1204: Ignite 1.5.33

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1204 Ignite 1.5.33 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.5.33 Alternatively you can review and

[GitHub] ignite pull request #563: ignite-2797 Fixed hanging of transactions with tim...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/563 --- 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 #873: Ignite 2968

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/873 --- 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 #888: Ignite 2968 part

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/888 --- 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 #933: Ignite-2968-1

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/933 --- 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 #943: Ignite-2968-2

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/943 --- 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 #964: Ignite-2968-3

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/964 --- 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 #1203: Ignite 3074

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/1203 Ignite 3074 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3074 Alternatively you can review and apply these

Re: Talking to Ignite From PHP

Denis, I believe that you should switch to DML branch (ignite-2294), and then merge ignite-3910 into it. That should be enough. Please let me know if there are any issues. Best Regards, Igor On Wed, Nov 2, 2016 at 3:12 AM, Denis Magda wrote: > Igor, > > I’m planning to

Re: IgniteSemaphore and failoverSafe flag

Vladisav, I've ran this test with partitioned cache and 1 backup and with replicated cache (4 nodes in topology). Behavior is the same. I think it is bug. But the first I wanted make sure that I understand failoverSafe flag correctly. Thank you for reply. I'll create ticket. On Tue, Nov 1, 2016

[jira] [Created] (IGNITE-4165) ignite-spark module scaladocs isn't included in Scala API docs

Andrey Gura created IGNITE-4165: --- Summary: ignite-spark module scaladocs isn't included in Scala API docs Key: IGNITE-4165 URL: https://issues.apache.org/jira/browse/IGNITE-4165 Project: Ignite

[jira] [Created] (IGNITE-4164) Add support for parallel loading of caches using custom SQL load queries in org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#loadCache

Anghel Botos created IGNITE-4164: Summary: Add support for parallel loading of caches using custom SQL load queries in org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#loadCache Key: IGNITE-4164 URL:

[jira] [Created] (IGNITE-4163) Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery

Anghel Botos created IGNITE-4163: Summary: Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery Key: IGNITE-4163 URL:

Re: Cache consistency

Hi Alisher, At first I assume the discussion need to be moved to user-forum ( u...@ignite.apache.org). If you have 2 backups (in case you have enough nodes) this mean you can loose 2 node, without afraid to loose data. In case you have a fail more than the 2 nodes, it is mean you have

Cache consistency

Hi! I have a question about data consistency in cluster, if there are any mechanism for checking that cache is in consistency state (no lost data/partitions) For example I have a cluster with N nodes, long compute job that calculate monthly revenue on huge amount of data. Data is transaction