Just came across OpenHub statistics in regards to Apache Ignite. More than a
year has already passed since Raul set the things up and now we can see our
ups and downs in a colorful way:
https://www.openhub.net/p/apache-ignite
My observations:
- code almost doubled in a number of lines.
- Vladimir
Igniters,
Imagine the following scenario:
startTx {
cache.get("key2");
cache.put("key1", val1);
cache.put("key2", val2);
commit();
}
In the transaction above key1 is updated first, and then key2. But since we
access key2 at the very beginning, cache store is updated in differen
Denis Magda created IGNITE-4587:
---
Summary: Discontinue and remove CacheAtomicWriteOrderMode.CLOCK
mode
Key: IGNITE-4587
URL: https://issues.apache.org/jira/browse/IGNITE-4587
Project: Ignite
I
I have submitted for a couple of talks myself.
I would like to encourage everyone in Ignite community, especially if you
don't mind visiting Miami, to submit a proposal. The topic may include
Ignite architecture, projects based on top of Ignite, as well as real
production use cases and deployments
Sam created IGNITE-4586:
---
Summary: REST on JBOSS instead of JETTY
Key: IGNITE-4586
URL: https://issues.apache.org/jira/browse/IGNITE-4586
Project: Ignite
Issue Type: Improvement
Components: r
Sam created IGNITE-4585:
---
Summary: Support CLEAR command with REST
Key: IGNITE-4585
URL: https://issues.apache.org/jira/browse/IGNITE-4585
Project: Ignite
Issue Type: Improvement
Components:
On Fri, Jan 20, 2017 at 7:00 AM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> Dmitriy,
>
> Honestly, I don't understand your issues with a reviewing, because I've
> provided PR link in the JIRA ticket.
>
> Just open it in browser and enjoy :)
>
> Nevertheless, I've added short descri
Hi Igniters,
I'm the guy who mostly contribute in C++ Ignite client and I
need your advice. Mostly I'd like to hear from our users and
those who are experienced in C++. Currently we have two
versions of most API methods - the throwing one and the
one that returns error through output argument. Thi
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1448
IGNITE-1466: Implemented BinaryObject for C++ client.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1466
Alter
IgniteCompute was designed this way initially. See IgniteCompute.future()
override. May be it makes sense to leave this type only for execute(...)
methods.
On Fri, Jan 20, 2017 at 5:45 PM, Semyon Boikov wrote:
> Hi Taras,
>
> Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? I
Dmitriy,
Honestly, I don't understand your issues with a reviewing, because I've
provided PR link in the JIRA ticket.
Just open it in browser and enjoy :)
Nevertheless, I've added short description for API changes in the JIRA
ticket.
Other comments are below.
2017-01-19 20:35 GMT+03:00 Dmitriy
Hi Taras,
Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
seems that ComputeTaskFuture is needed only for tasks?
On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov wrote:
> Gents
>
> I've done changes of the IgniteCompute as a subtask of the whole async API
> refactoring (
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/1447
IGNITE-4157 mapping updates notification hook
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4157
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1434
---
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 ena
Very cool! Clean and straightforward.
P.S.: If someone doesn't understand the fix - please look at new methods
with "async" suffix [1].
[1] https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a
35b20989f95ff52c0f6d91dd75d6/modules/core/src/main/java/
org/apache/ignite/IgniteCompute.java
On
Gents
I've done changes of the IgniteCompute as a subtask of the whole async
API refactoring (https://issues.apache.org/jira/browse/IGNITE-4580).
Please check the new version of the public API
(https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a35b20989f95ff52c0f6d91dd75d6/modules/core/
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1446
IGNITE-4580 Async API: IgniteCompute refactoring
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4580
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/1442
---
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 feat
Alexander, maybe you should use presorted collection in
TcpDiscoveryNodesRing.nextNode instead of iterating through unsorted one
every time?
Github user sergey-chugunov-1985 closed the pull request at:
https://github.com/apache/ignite/pull/1271
---
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
Yakov, I changed the implementation. Please, look at my code again.
https://github.com/apache/ignite/pull/1436
2017-01-19 15:37 GMT+03:00 Yakov Zhdanov :
> Alexander, as far as I remember we talked about having cluster id set via
> TcpDiscoverySpi configuration and also via system property.
>
>
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/1445
Ignite 4557
refactoring potentially dangerous polymorphic methods
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-45
Taras Ledkov created IGNITE-4584:
Summary: Async API: Tests refactoring to use new async API
Key: IGNITE-4584
URL: https://issues.apache.org/jira/browse/IGNITE-4584
Project: Ignite
Issue Type
Taras Ledkov created IGNITE-4583:
Summary: Async API: Other components refactoring
Key: IGNITE-4583
URL: https://issues.apache.org/jira/browse/IGNITE-4583
Project: Ignite
Issue Type: Sub-task
Taras Ledkov created IGNITE-4582:
Summary: Async API: IgniteFileSystem refactoring
Key: IGNITE-4582
URL: https://issues.apache.org/jira/browse/IGNITE-4582
Project: Ignite
Issue Type: Sub-task
Taras Ledkov created IGNITE-4581:
Summary: Async API: IgniteCache refactoring
Key: IGNITE-4581
URL: https://issues.apache.org/jira/browse/IGNITE-4581
Project: Ignite
Issue Type: Sub-task
Taras Ledkov created IGNITE-4580:
Summary: Async API: Refactoring IgniteCompute
Key: IGNITE-4580
URL: https://issues.apache.org/jira/browse/IGNITE-4580
Project: Ignite
Issue Type: Sub-task
Vladislav Pyatkov created IGNITE-4579:
-
Summary: Cluster ceased to process transaction, after massive
operations of cache on compute task
Key: IGNITE-4579
URL: https://issues.apache.org/jira/browse/IGNITE-4579
Andrew Mashenkov created IGNITE-4578:
Summary: SQL: Statement cache can cause memory leak
Key: IGNITE-4578
URL: https://issues.apache.org/jira/browse/IGNITE-4578
Project: Ignite
Issue Typ
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1438
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1439
---
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 ena
31 matches
Mail list logo
