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 T
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 we
Makes sense! I create the ticket:
https://issues.apache.org/jira/browse/IGNITE-2560
-Val
On Thu, Feb 4, 2016 at 6:22 PM, Dmitriy Setrakyan
wrote:
> Agree. I think we can avoid the performance degradation… If we cache the
> fact that EP does not have any resource annotations, then we can skip th
Valentin Kulichenko created IGNITE-2560:
---
Summary: Support injections in entry processors
Key: IGNITE-2560
URL: https://issues.apache.org/jira/browse/IGNITE-2560
Project: Ignite
Issue T
Agree. I think we can avoid the performance degradation… If we cache the
fact that EP does not have any resource annotations, then we can skip the
injection without any performance impact, no?
On Thu, Feb 4, 2016 at 5:48 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igniters,
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 thou
Valentin Kulichenko created IGNITE-2559:
---
Summary: Transaction hangs if entry processor is not serializable
Key: IGNITE-2559
URL: https://issues.apache.org/jira/browse/IGNITE-2559
Project: Ignite
Valentin Kulichenko created IGNITE-2558:
---
Summary: NearCacheConfiguration should not extend
MutableConfiguration
Key: IGNITE-2558
URL: https://issues.apache.org/jira/browse/IGNITE-2558
Project:
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.
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/364
---
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
Igniters,
Do we have API doc for .NET? If not, I think we should create it and put on
the website.
-Val
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 IGFS-accelerated (H)DFS?
To: u...@ignite.
Hi!
I looked through your latest pull request and left several comments on the
ticket.
-Val
On Fri, Jan 29, 2016 at 8:56 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Responded in the ticket.
>
> -Val
>
> On Fri, Jan 29, 2016 at 7:05 AM, Dood@ODDO wrote:
>
>> Val,
>>
>> Bef
Agree with Sergi. Mixing SQL with Java code transformers is confusing. In
rare case when it's really required, user can implement a custom function.
I copy-pasted the API to the ticket [1]. Please provide any additional
comments there.
[1] https://issues.apache.org/jira/browse/IGNITE-2546
-Val
Sergi,
> What you are going to transform remotely here?
I'm not going. I believe :)
Just hypothetical use case: You have one SqlFieldsQuery but different
requirements for returned values. For one case you have to return some
string fields as is and for another case you have to trim string to 3
Igor Sapego created IGNITE-2557:
---
Summary: ODBC: Add integrity tests.
Key: IGNITE-2557
URL: https://issues.apache.org/jira/browse/IGNITE-2557
Project: Ignite
Issue Type: Sub-task
Comp
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, TextQuery and SpiQuery ar
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 new
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: Ig
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 definition. So tran
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 not what it is.
>
I think I see
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 Andrey Gu
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&testNameId=206571224502097749&tab=testDetails
sockAddrs=[/127.0.0.1:4750
GitHub user oddodaoddo opened a pull request:
https://github.com/apache/ignite/pull/459
IGNITE-1144 Add affinity functions to collocated Ignite Queue and Set
Properly branched pull request as per instructions here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
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, Artem Shutak (JIRA)
>
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: Affinity.mapKeyToNode() metho
Sergey Kozlov created IGNITE-2555:
-
Summary: Include offheap usage in metrics report
Key: IGNITE-2555
URL: https://issues.apache.org/jira/browse/IGNITE-2555
Project: Ignite
Issue Type: Task
Artem Shutak created IGNITE-2554:
Summary: Affinity.mapKeyToNode() method throw
"ArithmeticException: / by zero" for LOCAL cache
Key: IGNITE-2554
URL: https://issues.apache.org/jira/browse/IGNITE-2554
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
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 add the new junit to tes
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 https://github.com/isapego/ig
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
R
Val,
can we introduce new method into IgnteCache API?
Now we have method: public QueryCursor query(Query qry);
New method will be something like this: QueryCursor query(Query
qry, Transformer transfomer);
It allows provide transformers for all query types and chnages will be
related only with
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 wrote:
Hi
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 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
Alte
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: Igni
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: Improv
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
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
Alternative
+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 wi
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.
> 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 approach.
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?
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 i
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 e
I think the whole point is to lock 1st and get 2nd. 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?
D.
On Thu, Feb 4, 2016 at 1:29 AM, Alexey Goncharuk wrote:
> If all keys are kno
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 keep hearing questions fr
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
Reporter:
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 possi
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, 2016 at 10:28 PM, Valentin
51 matches
Mail list logo