subscribe!
Anton, we are very far from agreement. I think it makes sense to step back,
come up with a clean design and propose it again.
On Fri, Jun 1, 2018 at 12:59 PM, Anton Vinogradov wrote:
> Dmitriy,
>
> Unfortunately, we have more than 2 types of txs, full list is
>
> GridDhtTxLocal
>
Hi,
I'm not involved with YCSB anymore. I suggest opening an issue on the
github repo itself; the maintainers are pretty responsive.
Brian
On Fri, Jun 1, 2018 at 3:29 AM, Ilya Suntsov wrote:
> Hi Brian,
>
> I would like to add Apache Ignite (https://apacheignite.readme.io/docs)
> client to
Dmitriy,
Unfortunately, we have more than 2 types of txs, full list is
GridDhtTxLocal
GridDhtTxRemote
GridNearTxLocal
GridNearTxRemote
BTW, We have no clear documentation about behaviour and difference.
I created an issue [1] to solve this, but seems no one interested :(
1) What I see is that
[CVE-2014-0114]: Apache Ignite is vulnerable to existing CVE-2014-0114
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected: Apache Ignite 2.4 or earlier
Impact:
An attacker can execute arbitrary code on Ignite nodes in the case when
Ignite classpath contains arbitrary
Prachi,
Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the document.
thanks!
在 2017/11/24 下午1:33, Prachi Garg 写道:
Attached.
On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
I do not like the inconsistent behavior between different transaction
events. I now feel that we need to separate events between Near TX and
Remote TX, and maybe focus on the Near TX for now.
How about we only add events for the Near TX and have a consistent behavior
across all Near TX events. I
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/4111
Ignite 8645
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-8645
Alternatively you can review and apply these changes as
Alexei Scherbakov created IGNITE-8684:
-
Summary: Partition state exchange during rebalance continues to
keep sending state messages (single,full) in loop even if no changes in
partitions states
Key: IGNITE-8684
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4110
IGNITE-8681: Introduce expiry throttling.
Thread will avoid try to clean expired entries if recent try has finished
with "nothing to clean".
You can merge this pull request into a Git
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4060
---
Github user Mikhail1988 closed the pull request at:
https://github.com/apache/ignite/pull/4107
---
GitHub user Mikhail1988 opened a pull request:
https://github.com/apache/ignite/pull/4109
Tests fail after IGNITE-6639
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-master-8683
Alternatively you
Mikhail Cherkasov created IGNITE-8683:
-
Summary: Test fails after IGNITE-6639
Key: IGNITE-8683
URL: https://issues.apache.org/jira/browse/IGNITE-8683
Project: Ignite
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4101
---
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4108
IGNITE-8682 Attempt to configure IGFS in persistent mode without specâ¦
â¦ific data region ends with AssertionError
You can merge this pull request into a Git repository by running:
$ git
Ivan Rakov created IGNITE-8682:
--
Summary: Attempt to configure IGFS in persistent mode without
specific data region ends with AssertionError
Key: IGNITE-8682
URL: https://issues.apache.org/jira/browse/IGNITE-8682
Andrew Mashenkov created IGNITE-8681:
Summary: Using ExpiryPolicy with persistence causes significant
slowdown.
Key: IGNITE-8681
URL: https://issues.apache.org/jira/browse/IGNITE-8681
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4106
---
Dmitriy,
1) EVT_TX_PREPARED were added this morning to check event generation on
remote nodes :)
2) Only GridNearTxLocal has label now, that's the implementation we
currently have. It can be improved if necesary, I think.
So, actually, label always available at
- EVT_TX_STARTED,
-
Ok, sounds good.
I till have more comments:
1. I think you have missed EVT_TX_PREPARED event
2. I am still very confused with your comment on "label()" method. Why
is the label not propagated to remote nodes? What happens when users call
this "label()" method for other TX events, not
GitHub user Mikhail1988 opened a pull request:
https://github.com/apache/ignite/pull/4107
IGNITE-8658 Add info message for complete partition exchange
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Dmitriy,
In that case there will be no chances to listen only tx creation events
without slowing down the system on other tx events creation and filtering.
All events are processed at same thread where tx changes the state, so, we
have to have the way to decrease potential slowdown.
I made it
Yury Babak created IGNITE-8680:
--
Summary: Encoding categorical features with OneHotEncoder
Key: IGNITE-8680
URL: https://issues.apache.org/jira/browse/IGNITE-8680
Project: Ignite
Issue Type:
Yury Babak created IGNITE-8679:
--
Summary: Integration with tensorflow datasets
Key: IGNITE-8679
URL: https://issues.apache.org/jira/browse/IGNITE-8679
Project: Ignite
Issue Type: New Feature
Vica Abramova created IGNITE-8677:
-
Summary: Web Console: Change Color Philosophy
Key: IGNITE-8677
URL: https://issues.apache.org/jira/browse/IGNITE-8677
Project: Ignite
Issue Type:
Hi Brian,
I would like to add Apache Ignite (https://apacheignite.readme.io/docs)
client to YCSB repository.
Pull request passed all travis tests:
https://github.com/brianfrankcooper/YCSB/pull/1118
Could you please take a look at this PR?
--
Best Regards,
Ilya Suntsov
email:
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4106
IGNITE-8664
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8664
Alternatively you can review and apply these
Andrey Aleksandrov created IGNITE-8676:
--
Summary: Possible data loss after stoping/starting several nodes
at the same time
Key: IGNITE-8676
URL: https://issues.apache.org/jira/browse/IGNITE-8676
29 matches
Mail list logo
