Re: FullText index can't be disabled for cache with String values.

Yes, this looks like a bad decision from the old times. I guess by default we should not create fulltext index for String, it must be explicitly enabled in QueryEntity if needed. Sergi 2017-02-17 10:18 GMT+03:00 Andrey Mashenkov : > Igniters, > > I've found that we can't use SORTED index only fo

PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Again, plz, review my PR : https://github.com/apache/ignite/pull/1517 https://issues.apache.org/jira/browse/IGNITE-1178 -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-4611 - ready for review

Hello everyone. I think it's ready for review: https://issues.apache.org/jira/browse/IGNITE-4611 - Write IgniteUuid with BinaryMarshaller ci.tests

Re: DML usability: routing single column to several object fields

Dima, I am not sure we are talking about the same thing. My point is that currently single value is often mapped to several values in cache key-value pair. This is done for usability reasons, and the question is how to continue supporting this approach with DML. Let me show the problem again, cons

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Alexander, This change is not applicable for GridFutureAdapter because resFlag can have 3 values there. 2017-02-16 19:58 GMT+03:00 Александр Меньшиков : > Hello. > > I propose to do refactoring of classes "GridFinishedFuture" and > "GridFutureAdapter". There is field "resFlag" which can equals "

Re: Implement IgniteZeromqStreamer to stream data from ZeroMQ

Sure, I will have a look in a couple of days.Maxim, thank you for the PR! Roman On Friday, February 17, 2017 12:39 AM, Denis Magda wrote: Roman, As the most experienced committer of the streaming components, could you do the review of Maxim’s changes? — Denis > On Feb 16, 2017, at 1

Re: Apache Ignite 1.9

IGNITE-4670 is merged to ignite-1.9 branch. On Thu, Feb 16, 2017 at 6:13 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Anton, > > However, I would like Serj or somebody else take a look at IGNITE-4106. > > On Thu, Feb 16, 2017 at 6:07 PM, Andrey Mashenkov < > andrey.mashen...@gmail

Took IGNITE-2845 Get operation might ignore entry update from EntryProcessor.

https://issues.apache.org/jira/browse/IGNITE-2845 -- *Best Regards,* *Kuznetsov Aleksey*

[jira] [Created] (IGNITE-4716) .NET: Add IgniteUuid system type support

Pavel Tupitsyn created IGNITE-4716: -- Summary: .NET: Add IgniteUuid system type support Key: IGNITE-4716 URL: https://issues.apache.org/jira/browse/IGNITE-4716 Project: Ignite Issue Type: Imp

4th Apache Ignite Meetup London hosted by IHS Markit on the 23rd of February

Fellow Igniters, We are very excited to invite you to join us for our 4th Apache Ignite Meetup hosted by IHS Markit on the 23rd of February. IHS Markit will present first on how they have been using Apache Ignite on several major projects. The 2nd part of the meetup will be led by Mandhir Gidd

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Aleksey, I added a comment on GitHub, however, the community is moving towards the UpSource review tool, so I suggest you open a PR review in Ignite UpSource: http://reviews.ignite.apache.org/ignite/ After you've registered, you should be able to open a review. --AG 2017-02-17 11:13 GMT+03:00 A

[GitHub] ignite pull request #1549: IGNITE-4611 to ignite-2.0

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1549 IGNITE-4611 to ignite-2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-4611 Alternatively you can review and appl

[GitHub] ignite pull request #1549: IGNITE-4611 to ignite-2.0

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

[jira] [Created] (IGNITE-4717) Cache size hangs on cache clear

Andrey Novikov created IGNITE-4717: -- Summary: Cache size hangs on cache clear Key: IGNITE-4717 URL: https://issues.apache.org/jira/browse/IGNITE-4717 Project: Ignite Issue Type: Bug

Re: Apache Ignite 1.9

Igniters, I tested Apache Ignite-1.9 and found possible bug https://issues.apache.org/jira/browse/IGNITE-4717 Could someone experienced in cache take a look?

[GitHub] ignite pull request #1550: IGNITE-2310: additional docs for affinity jobs

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1550 IGNITE-2310: additional docs for affinity jobs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2310-aff

Re: Locking of partition with affinityRun/affinityCall

Denis, Please review the javadoc of the affinity jobs. PR: https://github.com/apache/ignite/pull/1550 On 08.12.2016 12:06, Taras Ledkov wrote: Denis, The second point is absolutely correct. The rebalancing isn't blocked. The partition will not be evicted while the partition is reserved. I'

[GitHub] ignite pull request #1551: IGNITE-4611 for merge in 2.0

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1551 IGNITE-4611 for merge in 2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-4611-2.0 Alternatively you can review a

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Alexey, I see only one place where writes in resFlag: if (err != null) { resFlag = ERR; this.res = err; } else { resFlag = RES; this.res = res; } And th

Re: Inaccurate documentation about transactions

>From my point of view @IgniteTransactional annotation is redundant entity which will just confuse and lead to questions like "How to use this annotation?" I think documention update is better way. On Wed, Feb 15, 2017 at 1:50 PM, Evgeniy Stanilovskiy wrote: > postgres has the different viewpoint

[jira] [Created] (IGNITE-4718) Add section in documentation on what actions may cause deadlock

Dmitry Karachentsev created IGNITE-4718: --- Summary: Add section in documentation on what actions may cause deadlock Key: IGNITE-4718 URL: https://issues.apache.org/jira/browse/IGNITE-4718 Project

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

thanx! my next PR review will be in up source пт, 17 февр. 2017 г. в 13:05, Alexey Goncharuk : > Aleksey, > > I added a comment on GitHub, however, the community is moving towards the > UpSource review tool, so I suggest you open a PR review in Ignite UpSource: > http://reviews.ignite.apache.org/

Re: Apache Ignite 1.9

Denis/all, can we also get [1] in Ignite 1.9 ? [1] https://issues.apache.org/jira/browse/IGNITE-3862 -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-1-9-tp14170p14752.html Sent from the Apache Ignite Developers mailing list archive at Nabble

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Alexander, I think, the resFlag will be initiated as 0 (new GridFutureAdapter()), but 1 and 2 states will be acquired on live. On Fri, Feb 17, 2017 at 1:56 PM, Александр Меньшиков wrote: > Alexey, > > I see only one place where writes in resFlag: > > if (err != null) { >

[jira] [Created] (IGNITE-4719) Create documentation of current checks at Ignite-startup

Vyacheslav Daradur created IGNITE-4719: -- Summary: Create documentation of current checks at Ignite-startup Key: IGNITE-4719 URL: https://issues.apache.org/jira/browse/IGNITE-4719 Project: Ignite

Re: Apache Ignite 1.9

https://issues.apache.org/jira/browse/IGNITE-3862 already at 1.9, fixed "fixVersion". On Fri, Feb 17, 2017 at 2:40 PM, michael.griggs wrote: > Denis/all, can we also get [1] in Ignite 1.9 ? > > [1] https://issues.apache.org/jira/browse/IGNITE-3862 > > > > -- > View this message in context: http

[GitHub] ignite pull request #1552: IGNITE-4711 Propagate platform cache plugin confi...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1552 IGNITE-4711 Propagate platform cache plugin configuration to Java You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite igni

[jira] [Created] (IGNITE-4720) Sporadically fails for Hadoop

Irina Zaporozhtseva created IGNITE-4720: --- Summary: Sporadically fails for Hadoop Key: IGNITE-4720 URL: https://issues.apache.org/jira/browse/IGNITE-4720 Project: Ignite Issue Type: Bug

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Like I said, if "resFlag==0" (of course 0 came from initialization) means "you still haven't called the method onDone()", better make it clear. 2017-02-17 14:48 GMT+03:00 Vladislav Pyatkov : > Alexander, > > I think, the resFlag will be initiated as 0 (new GridFutureAdapter()), but > 1 and 2 sta

[GitHub] ignite pull request #1552: IGNITE-4711 Propagate platform cache plugin confi...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1552 --- 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 #1143: IGNITE-2940 .NET: Plugin system

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

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

We can check "onDone" method was called with using getState() method. If getState()!=0 then resFlag!=0. Just look at code. 2017-02-17 17:12 GMT+03:00 Александр Меньшиков : > Like I said, if "resFlag==0" (of course 0 came from initialization) means > "you still haven't called the method onDone()"

[GitHub] ignite pull request #1553: IGNITE-4169 Streamed SQL INSERTs

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1553 IGNITE-4169 Streamed SQL INSERTs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4169-to-1.9 Alternatively

[GitHub] ignite pull request #1350: IGNITE-4169 DML integration w/data streamer

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

Re: Inaccurate documentation about transactions

On Fri, Feb 17, 2017 at 3:35 AM, Andrey Gura wrote: > From my point of view @IgniteTransactional annotation is redundant > entity which will just confuse and lead to questions like "How to use > this annotation?" I think documention update is better way. > Why do you think it will be confusing?

Re: DML usability: routing single column to several object fields

Vladimir, Still not clear. Why not create a proper mapping of a table attribute to a key? If we don't support it today, do you think it will be feasible to add such support? D. On Fri, Feb 17, 2017 at 12:25 AM, Vladimir Ozerov wrote: > Dima, > > I am not sure we are talking about the same thin

Re: FullText index can't be disabled for cache with String values.

I have added a newbie label to this ticket. I think it should be simple enough to address. On Fri, Feb 17, 2017 at 12:05 AM, Sergi Vladykin wrote: > Yes, this looks like a bad decision from the old times. I guess by default > we should not create fulltext index for String, it must be explicitly

Re: DML data streaming

If we adapt table-per-cache policy, then table name should be equal to cache name, especially when table is created via SQL. For complex types, the type should also be equal to the table name. If the value type is primitive, then you can still use the table name in SQL and use the table name as ca

Re: 4th Apache Ignite Meetup London hosted by IHS Markit on the 23rd of February

Hi Chris, This is good news! Twitted: https://twitter.com/ApacheIgnite and added to the top of the news: https://ignite.apache.org/news.html — Denis > On Feb 17, 2017, at 1:46 AM, Christos Erotocritou > wrote: > > Fe