Igniters,
I noticed notifications about PRs in ignite-3 repository sent to
dev-list. I suppose we should configure notifications similar to main
ignite repository. I prepared a ticket [1] and PR for this. Please
review.
[1] https://issues.apache.org/jira/browse/IGNITE-13875
--
Best regards,
Iv
pavlukhin opened a new pull request #10:
URL: https://github.com/apache/ignite-3/pull/10
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to g
Ivan Pavlukhin created IGNITE-13875:
---
Summary: Configure notifications for ignite-3 git repository
Key: IGNITE-13875
URL: https://issues.apache.org/jira/browse/IGNITE-13875
Project: Ignite
Hi Igniters,
Forgive me that I am not reading dev list carefully these days. Was it
explicitly decided that Maven should be used as a build system for
Ignite 3? As there is a new repository we possibly can update our
build tools as well. What do you think?
2020-12-17 22:45 GMT+03:00, Valentin Kul
Hi,
I had posted this question in user list, posting it here again.
In 2.9.0 release of Ignite, ignite-kafka module was part of the ignite git.
Now when I check in master branch kafka module is not present, it has been
moved to https://github.com/apache/ignite-extensions
Also in maven repository
AMashenkov commented on a change in pull request #9:
URL: https://github.com/apache/ignite-3/pull/9#discussion_r545358324
##
File path: checkrules/pmd-ruleset.xml
##
@@ -0,0 +1,29 @@
+
+
AMashenkov commented on a change in pull request #9:
URL: https://github.com/apache/ignite-3/pull/9#discussion_r545358324
##
File path: checkrules/pmd-ruleset.xml
##
@@ -0,0 +1,29 @@
+
+
AMashenkov commented on a change in pull request #9:
URL: https://github.com/apache/ignite-3/pull/9#discussion_r545358324
##
File path: checkrules/pmd-ruleset.xml
##
@@ -0,0 +1,29 @@
+
+
AMashenkov commented on a change in pull request #9:
URL: https://github.com/apache/ignite-3/pull/9#discussion_r545357953
##
File path: checkrules/pmd-ruleset.xml
##
@@ -0,0 +1,29 @@
+
+
Review comment:
--
Hi Dmitriy,
I don't think there is any reason for concern at this point. The community
agreed on the scope of the changes for 3.0 - it is described on Wiki. The
scope is quite big, so it is clear that 2.x and 3.x will have to exist in
parallel for a significant amount of time, so we need a place w
Great news, Sergey!
-Val
On Thu, Dec 17, 2020 at 5:54 AM Sergey Chugunov
wrote:
> Val,
>
> Together with Semyon Danilov I did final polishing of code and merged it to
> the main branch in ignite-3 repo.
>
> Code assembles without any issues, tests are green, IgniteRunner starts and
> serves RES
Thanks, Kirill! Hopefully, this will be merged soon.
-Val
On Wed, Dec 16, 2020 at 4:54 AM Kirill Gusakov wrote:
> Hi, Valentin.
>
> PR is ready for review, some smoke tests added.
>
> On Sat, Dec 12, 2020 at 2:40 AM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Hi Kirill,
agoncharuk opened a new pull request #9:
URL: https://github.com/apache/ignite-3/pull/9
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
Alexey Goncharuk created IGNITE-13874:
-
Summary: Add PMD and idea inspections to Ignite-3 build cycle
Key: IGNITE-13874
URL: https://issues.apache.org/jira/browse/IGNITE-13874
Project: Ignite
Anton Vinogradov created IGNITE-13873:
-
Summary: Milti-cell transaction changes may be not visible (during
some time) after the Cellular switch
Key: IGNITE-13873
URL: https://issues.apache.org/jira/browse/IGNI
Yaroslav,
Send the pull-request to the master and then it needs to be cherry-picked
into the release branch. I clarified this in the process:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-ContributingSignificantChanges
-
Denis
On Wed, Dec 16, 2020 at 11:41 PM
Val,
Together with Semyon Danilov I did final polishing of code and merged it to
the main branch in ignite-3 repo.
Code assembles without any issues, tests are green, IgniteRunner starts and
serves REST requests successfully.
On Tue, Dec 15, 2020 at 10:37 PM Valentin Kulichenko <
valentin.kulich
Ivan Daschinskiy created IGNITE-13872:
-
Summary: Hardcoded retry timeout in ZookeeperClient
Key: IGNITE-13872
URL: https://issues.apache.org/jira/browse/IGNITE-13872
Project: Ignite
Issue
+1 (binding)
On Thu, 17 Dec 2020 at 12:07, Alex Plehanov wrote:
>
> +1 (binding)
>
> (checked build from source and start, checked build C++ from source and
> start, checked slim binary start, checked some examples)
>
>
> чт, 17 дек. 2020 г. в 10:41, Yaroslav Molochkov :
>
> > Denis,
> >
> > wher
Hello Slava,
Should we consider to include the MVCC public API removal to the 2.10 release?
[1] https://issues.apache.org/jira/browse/IGNITE-13871
On Thu, 17 Dec 2020 at 12:23, Вячеслав Коптилин
wrote:
>
> The vote is closed now.
>
> Vote result: Vote passed with 13 "+1" votes, no "0" and no "-
The vote is closed now.
Vote result: Vote passed with 13 "+1" votes, no "0" and no "-1" votes.
+1 Votes:
Valentin Kulichenko
Nikolay Izhikov
Andrey Gura
Igor Seliverstov
Andrey Mashenkov
Kirill Tkalenko
Nikita Amelchev
Petr Ivanov
Alexei Scherbakov
Maxim Muzafarov
Yuriy Gerzhedowich
Konstantin Or
Vyacheslav Koptilin created IGNITE-13871:
Summary: Removing MVCC public API
Key: IGNITE-13871
URL: https://issues.apache.org/jira/browse/IGNITE-13871
Project: Ignite
Issue Type: Bug
+1 (binding)
(checked build from source and start, checked build C++ from source and
start, checked slim binary start, checked some examples)
чт, 17 дек. 2020 г. в 10:41, Yaroslav Molochkov :
> Denis,
>
> where should i make my PR to update documentation? To my understanding
> there was a discu
23 matches
Mail list logo
