[GitHub] ignite pull request #1470: ignite-4538

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/1470 ignite-4538 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4538 Alternatively you can review and apply the

Re: ApacheCon CFP closing soon (11 February)

Igniters, If you’re use Apache projects (not only Ignite) for IoT purposes please go ahead and submit your IoT related talks to ApacheCon and IoTFuse. - 3 Feb: Submit a presentation proposal for IoTFuse https://iotfuse.com/call-for-proposals-2017-iotfuse-conference/

Re: DDL implementation details

Agree that schema-per-cache approach is natural for Ignite but will be a nightmare for those who migrate from a RDBMS. Inventing custom DDL statements is also a dead end. This won’t make users life and transitions from a RDBMS easier. Let’s to look at this differently. Most of us suggest the u

Re: eagerTtl

Val, could put a note regarding this behavior (thread per cache) to both JavaDoc and here? https://apacheignite.readme.io/docs/expiry-policies — Denis > On Jan 26, 2017, at 5:16 PM, vkulichenko > wrote: > > Surprisingly, the name of the thread is 'ttl-cleanup-worker' :) It's started > only if

Transactional tasks

Guys, How difficult would be to support transactional tasks? What means every job in task executed in it's own transaction. In case of single job failure or reduce phase failure all transaction started by jobs are rolled back. Only if all jobs are successfully executed, corresponding transactio

[jira] [Created] (IGNITE-4622) Web Console wrongly sets keyFields

Denis Magda created IGNITE-4622: --- Summary: Web Console wrongly sets keyFields Key: IGNITE-4622 URL: https://issues.apache.org/jira/browse/IGNITE-4622 Project: Ignite Issue Type: Bug

Re: Error Retrieving data from IgniteCache

Please attach the full stack trace and your Ignite configuration to that ticket and let us know when this is done. — Denis > On Jan 26, 2017, at 8:30 AM, hemanta wrote: > > Thank you for your email.I am seeing this error in the error log below. This > seems to generated by java using reflectio

Re: about lucene version dependent on ignite-indexing module

Please go ahead and take over this ticket: https://issues.apache.org/jira/browse/IGNITE-3562 If there will be no braking compatibility in terms of Ignite text search APIs that are built on top of Lucene then we will release the fix as soon as

Re: Error Retrieving data from IgniteCache

Thank you for your email.I am seeing this error in the error log below. This seems to generated by java using reflection. java.lang.ClassNotFoundException: sun.reflect.GeneratedMethodAccessor127 > INFO | jvm 1 | 2017/01/25 11:09:04 | at > org.apache.ignite.internal.processors.cache.GridCacheAdapter

[GitHub] ignite pull request #1469: IGNITE-4105 Introduced separate thread pool for S...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1469 IGNITE-4105 Introduced separate thread pool for SQL queries You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

[jira] [Created] (IGNITE-4621) Hang on broadcast when BinaryUtils.FIELDS_SORTED_ORDER == true

Anton Vinogradov created IGNITE-4621: Summary: Hang on broadcast when BinaryUtils.FIELDS_SORTED_ORDER == true Key: IGNITE-4621 URL: https://issues.apache.org/jira/browse/IGNITE-4621 Project: Ignit

[jira] [Created] (IGNITE-4620) CPP: Add documentation for DML

Igor Sapego created IGNITE-4620: --- Summary: CPP: Add documentation for DML Key: IGNITE-4620 URL: https://issues.apache.org/jira/browse/IGNITE-4620 Project: Ignite Issue Type: Task Comp

[GitHub] ignite pull request #1407: IGNITE-3430 .NET: Run Ignite transactions via sta...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1407 --- 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 ena

[GitHub] ignite pull request #1453: IGNITE-4511: Set QueryIndexType.SORTED by default...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1453 --- 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 #1468: IGNITE-4511: Set QueryIndexType.SORTED by default...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1468 IGNITE-4511: Set QueryIndexType.SORTED by default for an index You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignit

[jira] [Created] (IGNITE-4619) .NET: TransactionScope documentation and example

Pavel Tupitsyn created IGNITE-4619: -- Summary: .NET: TransactionScope documentation and example Key: IGNITE-4619 URL: https://issues.apache.org/jira/browse/IGNITE-4619 Project: Ignite Issue T

[GitHub] ignite pull request #1463: IGNITE-4157 DO NOT MERGE

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1463 --- 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

[GitHub] ignite pull request #1467: IGNITE-4558 Use BinaryArrayIdentityResolver by de...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1467 IGNITE-4558 Use BinaryArrayIdentityResolver by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/ezhuravl/ignite ignite-4558 Alternativ

[jira] [Created] (IGNITE-4618) CPP: Do not start JVM if it is already started

Vladimir Ozerov created IGNITE-4618: --- Summary: CPP: Do not start JVM if it is already started Key: IGNITE-4618 URL: https://issues.apache.org/jira/browse/IGNITE-4618 Project: Ignite Issue T

[GitHub] ignite pull request #1466: Ignite 4612

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/1466 Ignite 4612 -- Rename all ignored exception to "ignored" or keep "ignore" -- Rename all using exception named "ignore" or "ignored" -- Remove all unnecessary import (unused or same package

[jira] [Created] (IGNITE-4617) CPP: Implement Field-access methods for binary objects

Igor Sapego created IGNITE-4617: --- Summary: CPP: Implement Field-access methods for binary objects Key: IGNITE-4617 URL: https://issues.apache.org/jira/browse/IGNITE-4617 Project: Ignite Issue T

[GitHub] ignite pull request #1448: IGNITE-1466: Implemented BinaryObject for C++ cli...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1448 --- 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 ena

Re: about lucene version dependent on ignite-indexing module

Sergi， In the Ignite technology system, is not only the ignite-indexing module depends on the Lucene? From the API point of view, Lucene should be transparent to developers, but for some of the data format generated, it should be incompatible. 在 2017/1/26 19:07, Sergi Vladykin 写道: I'm not

[jira] [Created] (IGNITE-4616) Yardstick makes wrong restarts when several servers are at the same host

Ksenia Rybakova created IGNITE-4616: --- Summary: Yardstick makes wrong restarts when several servers are at the same host Key: IGNITE-4616 URL: https://issues.apache.org/jira/browse/IGNITE-4616 Projec

Re: about lucene version dependent on ignite-indexing module

I'm not a big Lucene expert, but such a major upgrade can be a breaking change for some users. I'd suggest to do it in 2.0. Sergi 2017-01-26 10:16 GMT+03:00 李玉珏@163 <18624049...@163.com>: > If the new version is not available, we can only use the 3.5.0 version, > because the major version of the

Re: Reactive APIs

Hi Sergei, Since the task is open and unassigned, I think you can go ahead with it. I've added you to Ignite project in Jira. Pavel On Thu, Jan 26, 2017 at 1:53 PM, Sergei Egorov wrote: > Hi all, > > I'm going to implement Reactive bindings. > > I see a task for RxJava: https://issues.apache.o

Reactive APIs

Hi all, I'm going to implement Reactive bindings. I see a task for RxJava: https://issues.apache.org/jira/browse/IGNITE-2331 Has anyone started it already? BR, Sergei

[GitHub] ignite pull request #1465: IGNITE-4552 support eviction for dhtLocalPartitio...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1465 IGNITE-4552 support eviction for dhtLocalPartition remove queue You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-455

Re: Updates reordering in transaction with cache store

Generally I agree with Yakov here, now order of updates is fully consistent with the order of cache locks acquisition. You change the transaction type => you change the order of cache locks => you change the order of db writes. I can assume that in some cases such a reordering may be useful, howev

[GitHub] ignite pull request #1079: Ignite 3922

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1079 --- 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 ena

Re: Updates reordering in transaction with cache store

Val, order is predictable - this is the order of update operations. You can do get() to lock all the keys in the order your DB is OK with. I can't say if new structure will affect performance or not, but it definitely can do so. --Yakov 2017-01-26 8:10 GMT+03:00 Valentin Kulichenko : > Yakov, >

[GitHub] ignite pull request #1464: Ignite-4571

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

Re: Should we take care of Java 9 in Ignite 2.0 scope?

Denis, I've created issue related to discussion. We have a lot of legacy code inside pom.xml files. One of legacy issues is a tools.jar usage. So, it will be nice to fix this as well. On Thu, Jan 26, 2017 at 2:54 AM, Denis Magda wrote: > Well,

[jira] [Created] (IGNITE-4615) Ignite should be compilable under JDK 9

Anton Vinogradov created IGNITE-4615: Summary: Ignite should be compilable under JDK 9 Key: IGNITE-4615 URL: https://issues.apache.org/jira/browse/IGNITE-4615 Project: Ignite Issue Type:

[GitHub] ignite pull request #1463: IGNITE-4157 DO NOT MERGE

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1463 IGNITE-4157 DO NOT MERGE This pull request was created to run tests on public TC only, it is not intended to be merged. You can merge this pull request into a Git repository by runnin