GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4885
GG-14260 backport IGNITE-9004
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14260
Alternatively you can
Thank you everyone for reviewing the changes. As discussed I have removed
the FlinkIgniteSourceSelfExample and also verified that
FlinkIgniteSourceSelfTestSuite
is part of Ignite Streamers in Team City.
Please let me know if any further changes are required.
Alex , will you please review and let
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Pavel Petroshenko created IGNITE-9758:
-
Summary: Document data injection via the REST API
Key: IGNITE-9758
URL: https://issues.apache.org/jira/browse/IGNITE-9758
Project: Ignite
Issue Typ
Thanks, got it.
On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov wrote:
> Here I agree with Vladimir. Furthermore, I do my absolute best to finalize
> all reviews in all 2.7 tickets I'm related to. I think most of the
> contributors doing the same.
>
> пн, 1 окт. 2018 г. в 23:03, Vladimir Ozerov :
Here I agree with Vladimir. Furthermore, I do my absolute best to finalize
all reviews in all 2.7 tickets I'm related to. I think most of the
contributors doing the same.
пн, 1 окт. 2018 г. в 23:03, Vladimir Ozerov :
> This is precisely the scope we have at the moment. All these tickets were
> co
This is precisely the scope we have at the moment. All these tickets were
considered carefully on whether to include them into AI 2.7 scope. I would
say that 10-15% of current tickets may be moved furhter.
Third of current tickets are features on their final review stages (e.g.
TDE, MVCC invoke, T
Thanks, Saikat, great blog!
On Sat, Sep 29, 2018 at 7:13 AM Saikat Maitra
wrote:
> Hi,
>
> We have published an article on Data streaming at Dzone. Thank you Prachi
> for help for publishing the article
>
>
> https://dzone.com/articles/data-streaming-using-apache-flink-and-apache-ignit
>
> Also
If this filter is for 2.7 release, then I do not believe all these tickets
will be closed. It would be nice to leave only "must-have" tickets in 2.7
and move the rest to 2.8.
D.
On Mon, Oct 1, 2018 at 11:02 AM Vladimir Ozerov
wrote:
> Igniters,
>
> Please use this filter, as it properly handles
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4884
Ignite 2.4.11
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.11
Alternatively you can review and apply th
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4883
Ignite 2.4.11
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.11
Alternatively you can review and apply th
Igniters,
Please use this filter, as it properly handles tickets without components:
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(com
Pavel Tupitsyn created IGNITE-9757:
--
Summary: С++: DetachCurrentThread is never called, causing Java
thread leak
Key: IGNITE-9757
URL: https://issues.apache.org/jira/browse/IGNITE-9757
Project: Ignit
Hello, Andrey.
Yes, I know it.
I've looked at the PR befor mailing :)
Do you think we can include this improvement to the 2.7 release?
Do you have time to assist Saikat with TC setup and other tasks?
В Пн, 01/10/2018 в 19:54 +0300, Andrey Mashenkov пишет:
> Dmitry, Nikolay,
>
> Ignite-3303 is
Dmitry, Nikolay,
Ignite-3303 is a new Ignite module and there is no changes related to core
or other existed modules.
So, PR should not affected existed functional ity and can be safely merged.
Thanks.
пн, 1 окт. 2018 г., 16:04 Dmitriy Pavlov :
> Hi Saikat,
>
> I don't mind merging to master,
I agree, which why I initially asked about code freeze (actually it was
scope freeze, I apologize).
So I prefer to create a new suite and give us some time to run these new
tests in master.
пн, 1 окт. 2018 г. в 19:34, Nikolay Izhikov :
> Alex, Saikat.
>
> As I can see there is work to be done to
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4577
---
Alex, Saikat.
As I can see there is work to be done to merge this feature.
So I think it's better to exclude it from 2.7.
Thoughts?
В Пн, 01/10/2018 в 18:35 +0300, Alexey Goncharuk пишет:
> Hello Saikat,
>
> I am ok with the prod code changes, but I am a bit confused with the
> example being ad
Pavel Pereslegin created IGNITE-9756:
Summary: [Test Failed]
IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in
master (timeout).
Key: IGNITE-9756
URL: https://issues.apache.org/jira
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4882
IGNITE-9754 Increase timeout waiting for commitLatch in
testRollbackOnTopologyLockPessimistic
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
Alexey Stelmak created IGNITE-9755:
--
Summary: PutAllSyncFailover test fail
Key: IGNITE-9755
URL: https://issues.apache.org/jira/browse/IGNITE-9755
Project: Ignite
Issue Type: Bug
Oleg Ignatenko created IGNITE-9754:
--
Summary: Increase timeout waiting for commitLatch in test
TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic
Key: IGNITE-9754
URL: https://issues.apache.
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4881
IGNITE-9540
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9540-1
Alternatively you can review and apply thes
Hi Nikolay,
Thank you for announcing that we entered this new stage of release. I
believe it is a paramount thing to keep community members posted.
BTW, this link worked for me
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVe
Hello Saikat,
I am ok with the prod code changes, but I am a bit confused with the
example being added to the tests folder. I think it should be either added
to the examples (not sure about the dependency though), or should not be
added at all. Also, I see that you added a new suite, has it been a
Hello, Igniters.
I announce scope freeze for an Apache Ignite 2.7 release.
It means:
1. We add to 2.7 only critical bugs.
2. We merge to 2.7 branch only previously announces features.
3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO OCTOBER 10*.
So the *October 10 is DEADLINE* fo
zzzadruga opened a new pull request #23: IGNITE-9541 Add row highlight for
'failed', add title for columns, re…
URL: https://github.com/apache/ignite-teamcity-bot/pull/23
…place JS code with JQuery
This is an automated messa
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4878
---
ARomantsov created IGNITE-9753:
--
Summary: Control.sh validate index work long and with errors
Key: IGNITE-9753
URL: https://issues.apache.org/jira/browse/IGNITE-9753
Project: Ignite
Issue Type:
Dmitry Sherstobitov created IGNITE-9752:
---
Summary: Fix ODBC documentation
Key: IGNITE-9752
URL: https://issues.apache.org/jira/browse/IGNITE-9752
Project: Ignite
Issue Type: Bug
Hello, Saikat.
I have no objections to include this integration to 2.7 release.
But, we should ask for a final review from Alex Goncharyuk.
Alex, can you comment on this?
Is this patch ready to be merged?
Do you see any risks to include it to 2.7 release?
В Вс, 30/09/2018 в 19:57 -0500, Saikat
Agree with Andrey.
IGNITE-9723 will be merged to ignite-2.7 branch soon.
On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov wrote:
>
> Igniters,
>
> There is an inaccuracy in critical worker termination detection, and I'm
> working on a fix right now, see [1]. Also, we have trivial yet important
> f
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4874
---
Hi Saikat,
I don't mind merging to master, but I have concern if it will go to 2.7. In
the separate discussion, we agreed on code freeze should happen during last
weekend, September, 30.
So it is now up to community and release manager to decide if fix should go
to the upcoming release. Usually,
Igniters,
There is an inaccuracy in critical worker termination detection, and I'm
working on a fix right now, see [1]. Also, we have trivial yet important
fix [2], this one is ready to merge.
I deem both should get to 2.7. Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-9744
[2
Dmitry Sherstobitov created IGNITE-9751:
---
Summary: Fix odic driver description
Key: IGNITE-9751
URL: https://issues.apache.org/jira/browse/IGNITE-9751
Project: Ignite
Issue Type: Bug
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4880
IGNITE-9126 Update Apache Kafka dependency
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9126
Alternatively
Folks,
We can consider this thread as an almost healthy discussion about SG
inclusion to 2.7.
For the future, I encourage all Igniters to discuss things before agreement
on dev.list instead of trying to log 'some pre-build agreements' here. BTW
such logged 'agreements' are not always valid.
Dev
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4879
ignite-9447: Fixed benchmarks setup freeze.
Now it is safe to call ignite().close() after setUp if multiply yardstick
driver hosts are used.
You can merge this pull request into a Git repo
Ivan Pavlukhin created IGNITE-9750:
--
Summary: Prohibit near cache configuration for MVCC caches
Key: IGNITE-9750
URL: https://issues.apache.org/jira/browse/IGNITE-9750
Project: Ignite
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4868
---
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4878
IGNITE-9741 SegmentAware recreated every activation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9741
Alterna
=1538379249752, loc=false, ver=2.7.0#20181001-sha1:9ab8ebd7,
isClient=false]]
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.backupNodes(GridDhtTxAbstractEnlistFuture.java:867)
[10:34:12]W
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4877
IGNITE-5534 added method to activate cluster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5534
Alternati
Great, I support this idea, will help with review too
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
45 matches
Mail list logo
