Re: ignite 1.4 status

Yakov, Valentin and I debugged the issue with ignite-1171 and I think we got to the bottom of it. First of all, pending messages were not reset to the correct collection on joining node which resulted in skipped custom event notifications. Second, the check that you have added to avoid discarding

Re: ignite 1.4 status

Igniters, While working on ignite-1171 we discovered couple more issues in discovery that might have threaten custom events processing under some circumstances (we have continuous processes based on this logic, for example). Alexey Goncharuk has picked this up. Another critical issue discovered

[jira] [Created] (IGNITE-1517) CacheInterceptor is not called on 'put' operations

Denis Magda created IGNITE-1517: --- Summary: CacheInterceptor is not called on 'put' operations Key: IGNITE-1517 URL: https://issues.apache.org/jira/browse/IGNITE-1517 Project: Ignite Issue Type:

Re: Asyncronous operations on distributed structures

I reviewed the changes and I agree. Anton V. can you please merge this PR? --Yakov 2015-09-18 15:26 GMT+03:00 Andrey Gura : > Done > > https://github.com/apache/ignite/pull/100 > > On Fri, Sep 18, 2015 at 12:36 PM, Yakov Zhdanov > wrote: > > > Absolutely agree ;) > > > > Andrey, can you please

[jira] [Created] (IGNITE-1516) Need to investigate performance drop for sql-query-offheap benchmark

Yakov Zhdanov created IGNITE-1516: - Summary: Need to investigate performance drop for sql-query-offheap benchmark Key: IGNITE-1516 URL: https://issues.apache.org/jira/browse/IGNITE-1516 Project: Ignit

Re: Hello!! Apache Ignite Dev

Please let us know your Jira ID. --Yakov 2015-09-18 21:58 GMT+03:00 Lalit Kumar Jha : > Hi Dmitriy, > > Thanks for the reply ang guide to get started. I setup project in IntelliJ > and Ignite in local machine. > > I want to work on Twitter Streamer >

Re: Hello!! Apache Ignite Dev

Hi Dmitriy, Thanks for the reply ang guide to get started. I setup project in IntelliJ and Ignite in local machine. I want to work on Twitter Streamer . Please add me to the Ignite contributors in Jira and assign this to me. Later, I want to work

[jira] [Created] (IGNITE-1515) IGFS: delete operations should be truly thread-safe

Ivan Veselovsky created IGNITE-1515: --- Summary: IGFS: delete operations should be truly thread-safe Key: IGNITE-1515 URL: https://issues.apache.org/jira/browse/IGNITE-1515 Project: Ignite Is

[GitHub] ignite pull request: IGNITE-586: version for "master" branch

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/101 IGNITE-586: version for "master" branch You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-586-master Alternativel

Re: SQL Hash indexes

Sergi, Does it mean that field "a" will now have 2 indexes, hash and sorted? D. On Fri, Sep 18, 2015 at 4:01 PM, Sergi Vladykin wrote: > Guys, > > It seems that for simple equality queries like > > SELECT * FROM x WHERE a = ? > > it is more effective to use hash indexes which do not even need

Re: Why IgniteAtomicLong is Closeable?

Agree, really strange. Even method close() without Closeable looks meaningless, if there is method removed() then it must have paired method remove() but not close(). Sergi 2015-09-18 17:22 GMT+03:00 Vladimir Ozerov : > Igniters, > > IgniteAtomicLong extends "Closeable" interface. Why? This appe

Re: Adding compare-and-set method returning value to distributed atomics

Pavel, just compare signatures, they serve different purposes. https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/atomic/AtomicLong.html#getAndUpdate-java.util.function.LongUnaryOperator- https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/atomic/AtomicLong.html#getAndSet-lo

Why IgniteAtomicLong is Closeable?

Igniters, IgniteAtomicLong extends "Closeable" interface. Why? This appears to be wrong, because normally user expects that Closeable/AutoCloseable resources are used as follows: try (Resource r = ...) { ... } For IgniteAtomicLong it means creation with immedaite destroy, definitely not what

[jira] [Created] (IGNITE-1514) Platform .Net: Implement IIgnite.DestroyCache

Pavel Tupitsyn created IGNITE-1514: --- Summary: Platform .Net: Implement IIgnite.DestroyCache Key: IGNITE-1514 URL: https://issues.apache.org/jira/browse/IGNITE-1514 Project: Ignite Issue Ty

SQL Hash indexes

Guys, It seems that for simple equality queries like SELECT * FROM x WHERE a = ? it is more effective to use hash indexes which do not even need to be snapshotable. I think it will be easy to implement one based on ConcurrentHashMap. Thoughts? Sergi

Re: Adding compare-and-set method returning value to distributed atomics

Sergi, we already have getAndSet, is getAndUpdate any different? On Fri, Sep 18, 2015 at 3:53 PM, Sergi Vladykin wrote: > Actually I can recall discussions related to this signature on java > concurrency interest mailing list, > there were some proponents of adding such a method into Atomics, bu

Re: Adding compare-and-set method returning value to distributed atomics

Actually I can recall discussions related to this signature on java concurrency interest mailing list, there were some proponents of adding such a method into Atomics, but the final resolution was that it is not that much different from existing compareAndSet to do the needed number of squats (it n

Re: Asyncronous operations on distributed structures

Done https://github.com/apache/ignite/pull/100 On Fri, Sep 18, 2015 at 12:36 PM, Yakov Zhdanov wrote: > Absolutely agree ;) > > Andrey, can you please do? > > --Yakov > > 2015-09-17 17:17 GMT+03:00 Dmitriy Setrakyan : > > > In this case, should we just simply update the documentation to reflect

[GitHub] ignite pull request: ignite-1500 Invalid docs in distributed data ...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/100 ignite-1500 Invalid docs in distributed data structures classes You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-1500

Re: Adding compare-and-set method returning value to distributed atomics

I was a bit wrong when describing non-Java semantics. "long CAS(old, new)" returns what was "old" at the moment of CAS attempt. In your case it will be: T1: CAS(0, 1) => 0 (success) T2: CAS(0, 1) -> 1 (failure) On Fri, Sep 18, 2015 at 12:30 PM, Yakov Zhdanov wrote: > Vladimir, > > Signature "lon

Re: Asyncronous operations on distributed structures

Absolutely agree ;) Andrey, can you please do? --Yakov 2015-09-17 17:17 GMT+03:00 Dmitriy Setrakyan : > In this case, should we just simply update the documentation to reflect the > reality? > > On Thu, Sep 17, 2015 at 3:30 PM, Andrey Gura wrote: > > > There is the same comment for the followi

Re: Getting this error while running unit test for storm module

We have org.apache.ignite.testframework.junits.GridAbstractTest#getTestTimeout to control test duration. You can override it to allow longer duration. However, I would recommend to make test less time consuming (or a bit more light weight) Thanks! --Yakov 2015-09-17 20:09 GMT+03:00 chandresh pa

[jira] [Created] (IGNITE-1513) Implement build procedure for platforms.

Vladimir Ozerov created IGNITE-1513: --- Summary: Implement build procedure for platforms. Key: IGNITE-1513 URL: https://issues.apache.org/jira/browse/IGNITE-1513 Project: Ignite Issue Type: S

Re: Adding compare-and-set method returning value to distributed atomics

Vladimir, Signature "long CAS(old, new)" does not work in my understanding. Imagine current value is 0 and 2 threads do CAS(0, 1). Both will get 1? How can I distinguish which thread really succeeds? Or one of the threads will get "0"? As far as .net API, I am OK to have .net approach for such fu

[jira] [Created] (IGNITE-1512) Rework IGFS remove operation.

Vladimir Ozerov created IGNITE-1512: --- Summary: Rework IGFS remove operation. Key: IGNITE-1512 URL: https://issues.apache.org/jira/browse/IGNITE-1512 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-1511) Revisit IGFS delete worker.

Vladimir Ozerov created IGNITE-1511: --- Summary: Revisit IGFS delete worker. Key: IGNITE-1511 URL: https://issues.apache.org/jira/browse/IGNITE-1511 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-1510) Weird format() and remove() semantics.

Vladimir Ozerov created IGNITE-1510: --- Summary: Weird format() and remove() semantics. Key: IGNITE-1510 URL: https://issues.apache.org/jira/browse/IGNITE-1510 Project: Ignite Issue Type: Tas

[jira] [Created] (IGNITE-1509) .Net: User must operate on IEnumerable in events API rather than on arrays.

Vladimir Ozerov created IGNITE-1509: --- Summary: .Net: User must operate on IEnumerable in events API rather than on arrays. Key: IGNITE-1509 URL: https://issues.apache.org/jira/browse/IGNITE-1509 Pro

[jira] [Created] (IGNITE-1508) .Net: Create common ToString() method.

Vladimir Ozerov created IGNITE-1508: --- Summary: .Net: Create common ToString() method. Key: IGNITE-1508 URL: https://issues.apache.org/jira/browse/IGNITE-1508 Project: Ignite Issue Type: Imp

Re: ignite 1.4 status

Alex, I think that your approach with delaying custom message will work. As far as coordinator crash protection, we guarantee delivery of certain messages types (including custom message). This logic was implemented long ago and seems to work. So, the message just gets resent. Semyon, can you plea

[jira] [Created] (IGNITE-1507) visorcmd: need to correct help text for 'tasks' command

Pavel Konstantinov created IGNITE-1507: -- Summary: visorcmd: need to correct help text for 'tasks' command Key: IGNITE-1507 URL: https://issues.apache.org/jira/browse/IGNITE-1507 Project: Ignite

[jira] [Created] (IGNITE-1506) visorcmd: inconsistent result of 'disco' command

Pavel Konstantinov created IGNITE-1506: -- Summary: visorcmd: inconsistent result of 'disco' command Key: IGNITE-1506 URL: https://issues.apache.org/jira/browse/IGNITE-1506 Project: Ignite