[GitHub] ignite pull request: IGNITE-1563 .Net: Implement "atomic" data str...

2016-02-04 Thread ptupitsyn
Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/204 --- 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: snapshot transaction isolation

2016-02-04 Thread Vladimir Ozerov
+1 This should help us with IGFS performance as we currently use getAll() in PESSIMISTIC mode mainly to lock keys, not to get their values. On Thu, Feb 4, 2016 at 12:56 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > So, basically, we want to add lockAll() method that locks entries

Re: snapshot transaction isolation

2016-02-04 Thread Alexey Goncharuk
In PESSIMISTIC transaction a value is always read after a lock is acquired, so a locked value cannot be updated. Am I missing something? Do you have a specific scenario in mind?

Re: snapshot transaction isolation

2016-02-04 Thread Yakov Zhdanov
> If you do a getAll, > isn’t it possible that some value will be updated before you get it? If > yes, then user’s logic will potentially be based on a wrong value, no? 1. What if any value gets updated before you lock it? It seems this is the strongest guarantee we can provide with this

[jira] [Created] (IGNITE-2550) .NET: Simplify examples configuration

2016-02-04 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-2550: -- Summary: .NET: Simplify examples configuration Key: IGNITE-2550 URL: https://issues.apache.org/jira/browse/IGNITE-2550 Project: Ignite Issue Type:

[GitHub] ignite pull request: IGNITE-2544: Empty schema names treated as a ...

2016-02-04 Thread isapego
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/456 IGNITE-2544: Empty schema names treated as a 'null' now. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2544

[jira] [Created] (IGNITE-2552) Eviction policy must consider either max size or max entries count

2016-02-04 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-2552: --- Summary: Eviction policy must consider either max size or max entries count Key: IGNITE-2552 URL: https://issues.apache.org/jira/browse/IGNITE-2552 Project: Ignite

[GitHub] ignite pull request: IGNITE-1563 .Net: Implemented "atomic" data s...

2016-02-04 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/455 IGNITE-1563 .Net: Implemented "atomic" data structures: sequence, reference You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

[jira] [Created] (IGNITE-2551) Next query page result link should be locked on loading of next page.

2016-02-04 Thread Vasiliy Sisko (JIRA)
Vasiliy Sisko created IGNITE-2551: - Summary: Next query page result link should be locked on loading of next page. Key: IGNITE-2551 URL: https://issues.apache.org/jira/browse/IGNITE-2551 Project:

[GitHub] ignite pull request: IGNITE-2451 remove xml and java data render f...

2016-02-04 Thread Dmitriyff
GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/457 IGNITE-2451 remove xml and java data render from controller You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-2451

Re: snapshot transaction isolation

2016-02-04 Thread Alexey Goncharuk
So, basically, we want to add lockAll() method that locks entries without returning their values to a client - this is a good idea. I do not want, however, to call it SNAPSHOT isolation, because this is not what it is.

[jira] [Created] (IGNITE-2549) CPP: Implement example that can be used for data visualization.

2016-02-04 Thread Igor Sapego (JIRA)
Igor Sapego created IGNITE-2549: --- Summary: CPP: Implement example that can be used for data visualization. Key: IGNITE-2549 URL: https://issues.apache.org/jira/browse/IGNITE-2549 Project: Ignite

Fwd: Apache Drill querying IGFS-accelerated (H)DFS?

2016-02-04 Thread Valentin Kulichenko
Igniters, Interesting question was posted on the user list (see below). Have we ever tested Hadoop Accelerator with Apache Drill? -Val -- Forwarded message -- From: pshomov Date: Thu, Feb 4, 2016 at 1:56 PM Subject: Apache Drill querying

API doc for .NET

2016-02-04 Thread Valentin Kulichenko
Igniters, Do we have API doc for .NET? If not, I think we should create it and put on the website. -Val

[jira] [Created] (IGNITE-2561) Optimize ATOMIC cache updates with single key.

2016-02-04 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-2561: --- Summary: Optimize ATOMIC cache updates with single key. Key: IGNITE-2561 URL: https://issues.apache.org/jira/browse/IGNITE-2561 Project: Ignite Issue

Re: Transformers in SCAN queries

2016-02-04 Thread Andrey Gura
Val, >From my point of view, special query class that allows transforming is confusing. Two points about it: 1. ScanTransformQuery will duplicate ScanQuery code with all drawbacks that we have. Moreover, any fix for ScanQuery should be repeated for ScanTransformQuery. It will lead to bugs. DRY.

Injections in entry processor

2016-02-04 Thread Valentin Kulichenko
Igniters, I noticed that we don't inject resources to entry processors. This doesn't look consistent, because do this everywhere else (closures, jobs, listeners, etc.). But at the same time I believe it will cause performance degradation, because we will have to inject on each operation. Any

[GitHub] ignite pull request: IGNITE-2549: Example that can be used for dat...

2016-02-04 Thread isapego
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/458 IGNITE-2549: Example that can be used for data visualization. Merged with IGNITE-2429. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-1144 Queue and Set affinity run and ca...

2016-02-04 Thread oddodaoddo
Github user oddodaoddo closed the pull request at: https://github.com/apache/ignite/pull/453 --- 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: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

2016-02-04 Thread Denis Magda
Hi Ken, Thanks for the contribution. Someone of the committers will review your changes soon. -- Denis On 2/3/2016 5:34 PM, Ken Cheng wrote: Sorry, my fault I forget to add the new junit to test suit. I committed again. Thanks, kcheng On Wed, Feb 3, 2016 at 10:17 PM, Ken Cheng

Re: [jira] [Created] (IGNITE-2554) Affinity.mapKeyToNode() method throw "ArithmeticException: / by zero" for LOCAL cache

2016-02-04 Thread Ken Cheng
Hi Artem Shutak , *Does this issue easy to reproduce? As I would like to work on it.* Thanks, kcheng On Thu, Feb 4, 2016 at 10:56 PM, Artem Shutak (JIRA) wrote: > Artem Shutak created IGNITE-2554: > > > Summary:

Re: [jira] [Created] (IGNITE-2554) Affinity.mapKeyToNode() method throw "ArithmeticException: / by zero" for LOCAL cache

2016-02-04 Thread Ken Cheng
fall into newbie tag? as I am a newbie to ignite.  Thanks, kcheng On Thu, Feb 4, 2016 at 11:10 PM, Ken Cheng wrote: > Hi Artem Shutak , > > *Does this issue easy to reproduce? As I would like to work on it.* > > > > > Thanks, > kcheng > > On Thu, Feb 4, 2016 at 10:56 PM,

Re: API doc for .NET

2016-02-04 Thread Vladimir Ozerov
We have doxygen plans which generate docs. Though, it appears that these docs are not published on the website. Who can assist us with this? On Fri, Feb 5, 2016 at 1:57 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > Do we have API doc for .NET? If not, I think

[jira] [Created] (IGNITE-2548) LINQ Examples

2016-02-04 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-2548: -- Summary: LINQ Examples Key: IGNITE-2548 URL: https://issues.apache.org/jira/browse/IGNITE-2548 Project: Ignite Issue Type: Sub-task

Re: snapshot transaction isolation

2016-02-04 Thread Alexey Goncharuk
If all keys are known in advance, how is it different from starting a pessimistic transaction and invoking getAll() on those keys? Introducing a new concept with such restrictions does not makes sense to me. 2016-02-04 1:27 GMT+03:00 Dmitriy Setrakyan : > Igniters, > > I

Re: Transformers in SCAN queries

2016-02-04 Thread Andrey Gura
SqlQuery, TextQuery and SpiQuery are similar to ScanQuery because all of them also defined as Query>. It can be usefull to have one query SqlQuery that can return different result that will be produced from cache entry by transformer. Actually only SqlFieldsQuery has different

[jira] [Created] (IGNITE-2556) The majority of method names in scalar module are (technically) invalid scala

2016-02-04 Thread Alec Zorab (JIRA)
Alec Zorab created IGNITE-2556: -- Summary: The majority of method names in scalar module are (technically) invalid scala Key: IGNITE-2556 URL: https://issues.apache.org/jira/browse/IGNITE-2556 Project:

Re: snapshot transaction isolation

2016-02-04 Thread Dmitriy Setrakyan
On Thu, Feb 4, 2016 at 1:56 AM, Alexey Goncharuk wrote: > So, basically, we want to add lockAll() method that locks entries without > returning their values to a client - this is a good idea. I do not want, > however, to call it SNAPSHOT isolation, because this is

[jira] [Created] (IGNITE-2553) Conditional functions

2016-02-04 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-2553: -- Summary: Conditional functions Key: IGNITE-2553 URL: https://issues.apache.org/jira/browse/IGNITE-2553 Project: Ignite Issue Type: Sub-task

Re: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

2016-02-04 Thread Ken Cheng
Thank you! Thanks, kcheng On Thu, Feb 4, 2016 at 9:38 PM, Denis Magda wrote: > Hi Ken, > > Thanks for the contribution. Someone of the committers will review your > changes soon. > > -- > Denis > > > On 2/3/2016 5:34 PM, Ken Cheng wrote: > >> Sorry, my fault I forget to

Assertion in TCP Discovery

2016-02-04 Thread Yakov Zhdanov
Igniters (esp Sam), I see this assertion when running tests. Can you please take a look at it? Here is the link to test history. Seems it is reproducible quiet often. http://204.14.53.151/project.html?projectId=IgniteTests=206571224502097749=testDetails sockAddrs=[/127.0.0.1:47501],

Re: Transformers in SCAN queries

2016-02-04 Thread Sergi Vladykin
I don't like the idea of having additional method *query(Query qry, Transformer transfomer); *because I don't see how these transformers will work for example with SQL, but this API makes you think that transformers are supported for all the query types. Sergi 2016-02-04 16:46 GMT+03:00

Re: [jira] [Created] (IGNITE-2554) Affinity.mapKeyToNode() method throw "ArithmeticException: / by zero" for LOCAL cache

2016-02-04 Thread Artem Shutak
Hi Ken, I've investigated the issue and a short answer is it's not a newbie issue. Detailed answer is there is 2 possible ways to fix it (at least): a simple fix and a not simple fix. I need to do the simple fix by yourself because it's need for related issue. The not simple fix is hard for

Re: Transformers in SCAN queries

2016-02-04 Thread Sergi Vladykin
The whole point of Transformer is to do remote transform, how will this work with SqlFieldsQuery? What you are going to transform remotely here? I believe all the transformations must happen at SQL level here. Sergi 2016-02-04 20:10 GMT+03:00 Andrey Gura : > SqlQuery,

Re: Transformers in SCAN queries

2016-02-04 Thread Semyon Boikov
I think scan query implementation can be more complex than just sending closures to all nodes. e.g. it should handle topology changes. IMO it is not good idea to use compute instead of queries. On Thu, Feb 4, 2016 at 10:55 AM, Dmitriy Setrakyan wrote: > On Wed, Feb 3,

Re: Transformers in SCAN queries

2016-02-04 Thread Andrey Kornev
Another perhaps bigger problem with running queries (including scan queries) using closures was discussed at length on the @dev not so long ago. It has to do with partitions migration due to cluster topology changes which may result in the query returning incomplete result. And while it is