Hi, Actually there is no such plan for 2.7. In 2.7 we will probably switch
to 1.1.1.
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 5:22, kcheng.mvp :
> Is there any plan to migrate kafka 2.0 in ignite-kafka?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
Ilya Borisov created IGNITE-9609:
Summary: Web console: update to AngularJS 1.7.4
Key: IGNITE-9609
URL: https://issues.apache.org/jira/browse/IGNITE-9609
Project: Ignite
Issue Type: Improveme
Alexander Kalinin created IGNITE-9608:
-
Summary: Fix buttons on start demo
Key: IGNITE-9608
URL: https://issues.apache.org/jira/browse/IGNITE-9608
Project: Ignite
Issue Type: Bug
Is there any plan to migrate kafka 2.0 in ignite-kafka?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/3159
---
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/3134
---
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/4707
---
Hi Alexei,
I did not find any PRs associated with the ticket for check code changes
behind this idea. Are there any PRs?
If we create some forwards scan of pages, it should be a very intellectual
algorithm including a lot of parameters (how much RAM is free, how probably
we will need next page, e
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/4767
IGNITE-7953: MVCC TX: continuous queriesÑ
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7953
Alternatively
HI Alex,
This is good that you observed speedup. But I do not think this solution
works for the product in general case. Amount of RAM is limited, and even a
single partition may need more space than RAM available. Moving a lot of
pages to page memory for scan means that you evict a lot of other p
Hi Andrew,
I have updated the tests and also added java docs.
Please review and share feedback.
Regards
Saikat
On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra
wrote:
> Hi Andrew, Alexey
>
> I have incorporated the review changes.
>
> I have also refactored the CacheEventSerializer class and mo
Alexey, this is a great feature. Can you explain what you meant by
"warm-up" when iterating through pages? Do you have this feature already
implemented?
D.
On Sun, Sep 16, 2018 at 6:44 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> Igniters,
>
> My use case involves scenario where
Igniters,
My use case involves scenario where it's necessary to iterate over
large(many TBs) persistent cache doing some calculation on read data.
The basic solution is to iterate cache using ScanQuery.
This turns out to be slow because iteration over cache involves a lot of
random disk access f
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/4316
---
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4766
PR
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14196
Alternatively you can review and apply t
Vyacheslav Daradur created IGNITE-9607:
--
Summary: Service Grid redesign - phase 1
Key: IGNITE-9607
URL: https://issues.apache.org/jira/browse/IGNITE-9607
Project: Ignite
Issue Type: Impr
GitHub user zjw4267127 opened a pull request:
https://github.com/apache/ignite/pull/4765
Ignite 2.3
asdf
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-2.3
Alternatively you can review and apply these change
17 matches
Mail list logo
