Hi,
First things first, let me clarify that I didn't request the feature myself
so I'm not advocating it ;-)
We have a vague proposition in a JIRA ticket, and my intention is to try
give it some objective essence. The team can happily close the ticket with
a "Won't Fix" if we feel that there's
Summarizing this:
*Goal*: All data flow/stream in system adhere to “Reactive Streams” API,
includes data ingestion, async computation, compute result/stream
aggregation.
*Benefits*:
- Common interface for all data transfer/exchange/processing.
- Streaming data ingestion can compose
It ' a nice feature to be included in the grid compute module , in my
opinion . But I have a question : what difference we have with ComputeTask
class in behavioral terms ?
https://apacheignite.readme.io/docs/compute-tasks
2015-09-23 16:45 GMT+02:00 Lalit Kumar Jha :
>
Lalit,
I don't think we are going to change our APIs to some 3rd party standards
or even worse to some 3rd party library.
There is already JCache from JSR-107 and I can't say we are 100% happy with
it.
Thus I can consider Reactive Streams to be an additional optional API but
not
`All data
Yakov, everyone is an admin in readme.io. Are you saying you cannot login?
D.
On Wed, Sep 23, 2015 at 4:49 AM, Yakov Zhdanov wrote:
> Dmitriy,
>
> Can you please check that I am still admin in readme io? I cant review the
> documentation for 1.4
>
> --Yakov
>
> 2015-09-20
As part of this discussion I want to talk about non-snapshotable indexes in
general.
There are few things we can do to improve performance of queries and
indexing.
1. We can implement SkipList based index. Probably it will not be much
faster than current SnapTree, but GC and Optimizer will feel
Alexey,
I have been running Vert.x cluster manager tests today. IGNITE-1171 doesn't
reproduces anymore.
But new problem was found: https://issues.apache.org/jira/browse/IGNITE-1534
I'll try to create Ignite test for this problem. I hope you have some ideas
about how to reproduce (stable) and
Gianfranco,
Behaviour wise it is similar. In this, data (streams) processed by map into
new stream and this new stream is processed by reduce stream.
In RS, multiple such opeartions are composed. This is as per MapReduce, RS
can exist alongside, by two means:
1. A new entity (reactive) in
Sergey,
Thanks for detailed explanation! I agree with your suggestion, let's do
on-heap (points 1 to 3) first and then switch to off-heap.
Can you please create a parent ticket with necessary subtasks, so we can
properly track it in Jira?
D.
On Wed, Sep 23, 2015 at 11:10 AM, Sergi Vladykin
Yes, we should not modify existing API, to support backward compatability
and richer functionality (the primary goal of product).
It will be additional wrapper/interface available.
This will also does not break anything and we can migrate slowly.
On Wed, Sep 23, 2015 at 9:08 PM, Sergi Vladykin
Alex, I merged 1171 to 1.4 branch.
We have very few tickets left.
Guys, who is in charge of checking this -
https://issues.apache.org/jira/browse/IGNITE-973? Please provide the update?
Hopefully, we will release tomorrow.
Thanks!
--Yakov
2015-09-23 8:37 GMT+03:00 Alexey Goncharuk
I'm working to reproduce IGNITE-973
On Wed, Sep 23, 2015 at 7:35 PM, Yakov Zhdanov wrote:
> Alex, I merged 1171 to 1.4 branch.
>
> We have very few tickets left.
>
> Guys, who is in charge of checking this -
> https://issues.apache.org/jira/browse/IGNITE-973? Please provide
I couldn't reproduce IGNITE-973 but would like to get a comment from the
reporter. Maybe some points for testing of issue have been missed by me...
On Wed, Sep 23, 2015 at 8:48 PM, Sergey Kozlov wrote:
> I'm working to reproduce IGNITE-973
>
> On Wed, Sep 23, 2015 at 7:35
Cos, is it ok that none of the domain names mentioned in ticket responds?
Even those with "dig" output.
Created ticket for Ignite -
https://issues.apache.org/jira/browse/INFRA-10484
--Yakov
2015-09-22 21:01 GMT+03:00 Konstantin Boudnik :
> Something like this could be
Valentin Kulichenko created IGNITE-1536:
---
Summary: Duplicate notification in continuous query
Key: IGNITE-1536
URL: https://issues.apache.org/jira/browse/IGNITE-1536
Project: Ignite
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/104
IGNITE-1536 - Removed duplicated continuous query notifications
You can merge this pull request into a Git repository by running:
$ git pull
Alexey Goncharuk created IGNITE-1537:
Summary: Near TX prepare future is completed early for LOCAL cache
Key: IGNITE-1537
URL: https://issues.apache.org/jira/browse/IGNITE-1537
Project: Ignite
Sergey Kozlov created IGNITE-1535:
-
Summary: Evicted entries still are presented
Key: IGNITE-1535
URL: https://issues.apache.org/jira/browse/IGNITE-1535
Project: Ignite
Issue Type: Bug
Anton,
Clone this repo https://github.com/chandresh-pancholi/ignite and run this
class
https://github.com/chandresh-pancholi/ignite/blob/master/modules/storm/src/test/java/org/apache/ignite/stream/storm/IgniteStormStreamerSelfTestSuite.java
You will get the Error saying "Oouch,Argument is Null"
19 matches
Mail list logo