Alexey Kuznetsov created IGNITE-9808:
Summary: Web Console: Refactor sockets caching
Key: IGNITE-9808
URL: https://issues.apache.org/jira/browse/IGNITE-9808
Project: Ignite
Issue Type:
Alexey Kuznetsov created IGNITE-9809:
Summary: Web Console: Minor Fixes
Key: IGNITE-9809
URL: https://issues.apache.org/jira/browse/IGNITE-9809
Project: Ignite
Issue Type: Task
Alexey Kuznetsov created IGNITE-9807:
Summary: Web Agent: Add support for cluster ID
Key: IGNITE-9807
URL: https://issues.apache.org/jira/browse/IGNITE-9807
Project: Ignite
Issue Type:
Hi folks,
Recently time ago, I noticed that many Jira issues created and filled in
different ways,
so someone does not fill issue description, someone does not attach links
in the links section instead, add links to comments and etc.
I want to star discussion regards to Jira issue filling rules.
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4921
Test caches dirs cleanup on blt changed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite blt_chng_test
Alternatively you can
++1 from my side, as always.
I want to add GitHub as a possible place of discussion, but any place we've
selected to run review should be mentioned in JIRA ticket. E.g., I left a
couple of comments in PR; please take a look.
вс, 7 окт. 2018 г. в 18:01, Dmitriy Govorukhin :
> Hi folks,
>
>
Alexei Scherbakov created IGNITE-9806:
-
Summary: Legacy tx invalidation code breaks data consistency
between owners.
Key: IGNITE-9806
URL: https://issues.apache.org/jira/browse/IGNITE-9806
