Agreed that that seems the most likely course.
A random set of individuals who may or may not overlap with the individuals
who are a part of Apache Ignite launch a new project on GitHub and Apache
Ignite depend on it akin to their dependency on H2.
Which seems like a decision made by inertia -
Denis, I'm not negative in relation to GridGain, if Sberbank will suggest
Ignite (or any other Apache project I'm involved too) code to be dependent
on
'com.sberbank.whatsoever.coollibrary'
binary, they can count on my veto, as well.
There is no difference in company suggesting this:
Ok, folks, let's create a separate Github repo for the H2 fork and ensure
the binaries of that fork are used by Ignite. As for the discussion with
ASF legal, nobody suggested any alternatives and I'm signing off that
discussion:
Rob,
That's the right question. Basically, future plans of H2 community doesn't
align with Ignite needs. We made several contributions to the upstream,
but the next changes are not of H2 roadmap interest. Ignite community will
be adopting H2 fork for the distributed SQL engine needs (special
Dmitriy,
Thank you for sharing your vision.
Actually I think that an agreement within the community is the most
important thing.
ср, 10 июл. 2019 г. в 17:44, Dmitriy Pavlov :
>
> Hi Ivan,
>
>
>
> I don’t need a policy to clearly understand that the Apache project stops
> to be healthy once it
Hi Ivan,
I don’t need a policy to clearly understand that the Apache project stops
to be healthy once it is controlled by one entity. This is related to
governance, not to OSI approved license (if a lib is open-source or not).
Apache mission - Create software for the public good.
Apache
Folks,
Investigating now unexpected repairs [1] in case of ReadRepair usage at
testAccountTxNodeRestart.
Updated [2] the test to check is there any repairs happen.
Test's name now is "testAccountTxNodeRestartWithReadRepair".
Each get method now checks the consistency.
Check means:
1) tx lock
Igor Kamyshnikov created IGNITE-11974:
-
Summary: infinite loop and 100% cpu in GridDhtPartitionsEvictor:
Eviction in progress ...
Key: IGNITE-11974
URL: https://issues.apache.org/jira/browse/IGNITE-11974
Perhaps, it would be a good idea to think about the recovery tool/
control-utility command that will allow achieving the same goal.
If I am not mistaken it was already proposed in the email thread.
Thanks,
S.
ср, 10 июл. 2019 г. в 15:33, Вячеслав Коптилин :
> Hi Anton,
>
> Well, the ReadRepair
Hi Anton,
Well, the ReadRepair feature is finally merged and that is good news :)
Unfortunately, I cannot find a consensus about the whole functionality in
any of these topics:
-
http://apache-ignite-developers.2346864.n4.nabble.com/Consistency-check-and-fix-review-request-td41629.html
-
Ivan.
> I suppose that I did not ever claim such thing
Thanks for clarifing :)
> GitHub project outside any commercial company accounts, there all Apache
> committers added as collaborators may work.
> Sounds nice for me as well.
+1 from me if it compatible with Apache policies.
В Ср,
Nikolay,
> Why we should close H2 fork from Ignite commiters in the first place?
I suppose that I did not ever claim such thing. I think we are
discussing various options. And ones might be simpler and others might
be harder.
Dmitriy,
To my shame I am not very competent in licensing and related
Hi Liyuj,
As of now we don't support COMMENT ON statements and don't have such plans
or a tickets to add one. But I agree that it should add facilities for
users.
Feel free to raise the ticket.
ср, 10 июл. 2019 г. в 00:48, Dmitriy Pavlov :
> Hi,
>
> I'm not aware of such plans, for now.
>
>
Wearing the hat of Apache Ignite PMC:
I'm against starting with dependency on GridGain code in any case. Gridgain
can do its own forks of both.
We all know how much influence the company has on the community and adding
one more (I remind there is gridgain:shmem)
means the open-governed solution
Ivan.
> Could you please elaborate why is it "closed source"?
This fork sources will changed on the purpose and willness of Grid Gain not
Ignite community.
> Actually, my only point is that we can do it at any point later, cannot
we?
Why we should close H2 fork from Ignite commiters in the
Agree with Ivan.
We can start work with H2 fork owned by GG and decide change it later in
case it will bring some issues to Ignite community. Currently I don't see
any issues here.
I'm worried about the issue, with process to synchonize changes H2 fork and
Ignite. As possible solution it could
Nikolay,
Could you please elaborate why is it "closed source"?
> What the difference for the Ignite community?
The difference is similar to using version X and version Y of the same
library. Version Y might be better.
> I think all Ignite commiters should have write priveledges to H2 fork.
I
Ivan
We have closed source code dependency for now owned by H2 owners.
With new fork we will have the same closed dependency owned by Grid Gain.
What the difference for the Ignite community?
> 2. Anyways some process must be established for merging changes
> requiring changes in h2 library. So,
Folks,
I would like to highlight a couple of points.
1. Perhaps it is not so crucial where is this fork located if the code
is publicly available and can be cloned to another repository easily.
We can relocate code and use it at any point in future.
2. Anyways some process must be established for
Denis
Stepping backwards from the legal question: why does the Ignite community feel
that they need to fork H2?
Can the community simply not work to contribute your desired changes to the
upstream H2 community?
Rob
From: Denis Magda
Reply-To:
Date: Wednesday, 10 July 2019 at
Folks,
Thanks to everyone for tips and reviews.
Yardstick checked, no performance drop found.
Additional measurement: RR get() is just up to 7% slower than regular get
on real benchmarks (8 clients, 4 servers, 3 backups)
Code merged to the master.
"Must have" tasks created and attached to the
Anton Vinogradov created IGNITE-11973:
-
Summary: testAccountTxNodeRestart cause unexpected repairs in case
of ReadRepair usage
Key: IGNITE-11973
URL: https://issues.apache.org/jira/browse/IGNITE-11973
Anton Vinogradov created IGNITE-11972:
-
Summary: Jepsen tests should check consistency
Key: IGNITE-11972
URL: https://issues.apache.org/jira/browse/IGNITE-11972
Project: Ignite
Issue
Hello, Denis.
> Nickolay, as for that fork which is in GG codebase - GridGain is a major
> contributor and maintainer but the others are welcomed to send
> pull-requests.
Can we make this fork maintained by Ignite Community?
With all respect to Grid Gain as an author of Apache Ignite I don't
Anton Vinogradov created IGNITE-11971:
-
Summary: Consistency check on test finish
Key: IGNITE-11971
URL: https://issues.apache.org/jira/browse/IGNITE-11971
Project: Ignite
Issue Type:
25 matches
Mail list logo
