Re: Python thin client

[Dmitry Melnichuk]

Igor,

I am in doubt here because I am not fully comprehend the meaning of 
"binary release". But if it is somehow related to the "distribution" 
thing, I would dare to suggest the following options:


1. Copy nothing. Just do

```
$ python setup.py bdist_wheel
$ twine upload dist/*
```

during the build process (or separately) and let PyPI handle the 
distribution.


This is the most natural and user-friendly way of distributing Python 
packages. End user might only do


```
$ pip install pyignite
```

as it is suggested by my readme file.

2. Supply the wheel package. It is the file 'pyignite-*.whl' from 'dist' 
directory, that should appear there as the "python setup.py bdist_wheel" 
command finishes. Actually, it can be combined with the first option.


The wheel can then be installed by the end user:

```
$ pip install pyignite-*.whl
```

3. Supply the following files:

ignite/modules/platforms/python/pyignite/**
ignite/modules/platforms/python/requirements/**
ignite/modules/platforms/python/LICENSE
ignite/modules/platforms/python/README.md
ignite/modules/platforms/python/setup.py

(** stands for "all the files and sub-folders recursively, starting from 
this folder".)


It is not uncommon or wrong to distribute Python programs as text 
without prior packaging, but, in my personal experience, this is a way 
more suitable for one-time scripts or proprietary programs. For example, 
most of Python web apps relies on git for deployment, without any 
packaging subsystem.


Here's a few words about wheels:

https://wheel.readthedocs.io/

Here's about uploading to PyPI with twine:

https://packaging.python.org/tutorials/packaging-projects/#uploading-the-distribution-archives

On 9/14/18 9:05 PM, Igor Sapego wrote:

Ok, good.

Now, what is about installation? Which directories/files
need to be copied to ignite's binary release?

Best Regards,
Igor

[MTCGA]: new failures in builds [1871897] needs to be handled

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New test failure in master IgniteStandByClusterTest.testSimple 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1332314705000986815=%3Cdefault%3E=testDetails
 Changes may led to failure were done by 
 - bessonov.ip 
http://ci.ignite.apache.org/viewModification.html?modId=831651=false

- If your changes can led to this failure(s), please create issue with 
label MakeTeamCityGreenAgain and assign it to you.
-- If you have fix, please set ticket to PA state and write to dev list 
fix is ready 
-- For case fix will require some time please mute test and set label 
Muted_Test to issue 
- If you know which change caused failure please contact change author 
directly
- If you don't know which change caused failure please send message to 
dev list to find out
Should you have any questions please contact dev@ignite.apache.org 
Best Regards,
MTCGA.Bot 
Notification generated at Sat Sep 15 05:42:21 MSK 2018 

Re: Data streaming using Apache Ignite and Flink

[Saikat Maitra]

Thank you so much for publishing the blog in Ignite blogs page.

I also posted an article about How I started with Apache Ignite in Target
tech blog.

https://tech.target.com/2018/09/14/data-streaming-using-apache-flink-and-apache-ignite.html

Regards,
Saikat

On Fri, Sep 14, 2018 at 2:35 PM, Prachi Garg  wrote:

> Here's the link to the blogs page -  https://ignite.apache.org/blogs.html
>
> On Wed, Sep 12, 2018 at 12:12 PM, Denis Magda  wrote:
>
> > Prachi,
> >
> > Did you forget to add Saikat's blog to the list?
> >
> > --
> > Denis
> >
> > On Wed, Sep 12, 2018 at 1:44 PM Dmitriy Pavlov 
> > wrote:
> >
> >> Hi Denis,
> >>
> >> I didn't find the blog post there.
> >>
> >> Could you please add it or advice me how can I do it?
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> вт, 28 авг. 2018 г. в 4:19, Saikat Maitra :
> >>
> >> > Thank you so much Denis.
> >> >
> >> > Regards,
> >> > Saikat
> >> >
> >> > On Mon, Aug 27, 2018 at 5:00 PM, Denis Magda 
> wrote:
> >> >
> >> > > Hello Saikat,
> >> > >
> >> > > Thanks for the article and contribution. We'll get it added to:
> >> > > https://ignite.apache.org/blogs.html
> >> > >
> >> > > --
> >> > > Denis
> >> > >
> >> > > On Sun, Aug 26, 2018 at 2:59 PM Saikat Maitra <
> >> saikat.mai...@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > Hello,
> >> > > >
> >> > > > I recently published blog on how we can stream data using Apache
> >> Ignite
> >> > > and
> >> > > > Flink. This uses IgniteSink with recent changes merged (release
> due
> >> in
> >> > > > 2.7.0) which will allow us to run IgniteSink using Apache Flink in
> >> > > cluster
> >> > > > mode.
> >> > > >
> >> > > >
> >> > > >
> >> > > > https://samaitra.blogspot.com/2018/08/data-streaming-using-
> >> > > apache-flink-and.html
> >> > > >
> >> > > > Please review and let me know if you have feedback.
> >> > > >
> >> > > > Regards,
> >> > > > Saikat
> >> > > >
> >> > >
> >> >
> >>
> >
>

[GitHub] ignite pull request #4733: IGNITE-7618 validateCache synchronously waits for...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4733


---

Обновленное приглашение: Apache Ignite TeamCity Bot: Features overview - вт, 18 сент 2018 17:00 - 18:00 (MSK) (dev@ignite.apache.org)

[dpavlov . spb]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180918T14Z
DTEND:20180918T15Z
DTSTAMP:20180914T103142Z
ORGANIZER;CN=Dmitriy Pavlov:mailto:dpavlov@gmail.com
UID:2dm8hva8m323mg63ukrfuje...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=dev@ignite.apache.org;X-NUM-GUESTS=0:mailto:dev@ignite.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Dmitriy Pavlov;X-NUM-GUESTS=0:mailto:dpavlov@gmail.com
CLASS:PUBLIC
CREATED:20180914T092358Z
DESCRIPTION:Most of you have noticed emails from the Bot to dev@ignite.apache.org. We will cove
 r details and features of this new monitoring and PR checking tool https://mtcga.gridgain.com/;>https://mtcga.gridgain.com/- We w
 ill know how test failure is considered as a blocker by the bot.- When 
 emails will appear on the dev list and how to avoid it.- On this webina
 r we will cover major implemented and some planned features.The mee
 ting is intended for Apache Ignite Developers\, TC Bot enthusiasts and ever
 yone interested.Language: EnglishTime: Tue\, Sep 18\, 2018 5:00
  PM - 5:30 PM MSK Please join my meeting from your computer\, table
 t or smartphone. https://global.gotomeeting.com/join/364140429
 ">https://global.gotomeeting.com/join/364140429 You can also di
 al in using your phone. United States: +1 (669) 224-3412 Access
  Code: 364-140-429 First GoToMeeting? Let's do a quick system check
 : https://link.gotomeeting.com/system-check;>https://link.goto
 meeting.com/system-check\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nНе редактируйте этот раздел о
 писания.\n\nПросмотрите свое мероприятие на странице https://www.google.com
 /calendar/event?action=VIEW=MmRtOGh2YThtMzIzbWc2M3VrcmZ1amV0aWYgZGV2QGl
 nbml0ZS5hcGFjaGUub3Jn=MjEjZHBhdmxvdi5zcGJAZ21haWwuY29tY2Y4MzIwZjE0ZWZiM
 TY0ZDA2Yzk2MTMxMzcwZGU3ZmZjN2M5YWQzMw=Europe%2FMoscow=ru=0.\n-::~
 :~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 ::~:~::-
LAST-MODIFIED:20180914T103141Z
LOCATION:https://global.gotomeeting.com/join/364140429 
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Apache Ignite TeamCity Bot: Features overview 
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H30M0S
END:VALARM
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H10M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

Re: Data streaming using Apache Ignite and Flink

[Prachi Garg]

Here's the link to the blogs page -  https://ignite.apache.org/blogs.html

On Wed, Sep 12, 2018 at 12:12 PM, Denis Magda  wrote:

> Prachi,
>
> Did you forget to add Saikat's blog to the list?
>
> --
> Denis
>
> On Wed, Sep 12, 2018 at 1:44 PM Dmitriy Pavlov 
> wrote:
>
>> Hi Denis,
>>
>> I didn't find the blog post there.
>>
>> Could you please add it or advice me how can I do it?
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> вт, 28 авг. 2018 г. в 4:19, Saikat Maitra :
>>
>> > Thank you so much Denis.
>> >
>> > Regards,
>> > Saikat
>> >
>> > On Mon, Aug 27, 2018 at 5:00 PM, Denis Magda  wrote:
>> >
>> > > Hello Saikat,
>> > >
>> > > Thanks for the article and contribution. We'll get it added to:
>> > > https://ignite.apache.org/blogs.html
>> > >
>> > > --
>> > > Denis
>> > >
>> > > On Sun, Aug 26, 2018 at 2:59 PM Saikat Maitra <
>> saikat.mai...@gmail.com>
>> > > wrote:
>> > >
>> > > > Hello,
>> > > >
>> > > > I recently published blog on how we can stream data using Apache
>> Ignite
>> > > and
>> > > > Flink. This uses IgniteSink with recent changes merged (release due
>> in
>> > > > 2.7.0) which will allow us to run IgniteSink using Apache Flink in
>> > > cluster
>> > > > mode.
>> > > >
>> > > >
>> > > >
>> > > > https://samaitra.blogspot.com/2018/08/data-streaming-using-
>> > > apache-flink-and.html
>> > > >
>> > > > Please review and let me know if you have feedback.
>> > > >
>> > > > Regards,
>> > > > Saikat
>> > > >
>> > >
>> >
>>
>

[GitHub] ignite pull request #4764: IGNITE-8879 Blinking baseline node sometimes unab...

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

https://github.com/apache/ignite/pull/4764

IGNITE-8879 Blinking baseline node sometimes unable to connect to clu…

…ster

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10919

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4764.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4764


commit 1f3d38848ebdc0d145b58e15d0d6749ca55d9c61
Author: vd-pyatkov 
Date:   2018-09-14T18:28:26Z

IGNITE-8879 Blinking baseline node sometimes unable to connect to cluster




---

[GitHub] asfgit closed pull request #10: IGNITE-9588 Separate page for JIRA, GitHub actions

[GitBox]

asfgit closed pull request #10: IGNITE-9588 Separate page for JIRA, GitHub 
actions
URL: https://github.com/apache/ignite-teamcity-bot/pull/10
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITcHelper.java 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITcHelper.java
index 69df43d..1077a0e 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITcHelper.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITcHelper.java
@@ -59,4 +59,14 @@
 Collection getServerIds();
 
 List getTrackedBranchesIds();
+
+/**
+ * @param srvId Server id.
+ * @param prov Credentials.
+ * @param buildTypeId Suite name.
+ * @param branchForTc Branch for TeamCity.
+ * @param ticket JIRA ticket full name.
+ * @return {@code True} if JIRA was notified.
+ */
+boolean notifyJira(String srvId, ICredentialsProv prov, String 
buildTypeId, String branchForTc, String ticket);
 }
diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
index 8201f5c..6a475a4 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
@@ -287,11 +287,11 @@ default SingleBuildRunCtx loadTestsAndProblems(@Nonnull 
Build build, @Deprecated
 PullRequest getPullRequest(String branch);
 
 /**
- * @param ticket JIRA ticket name.
+ * @param ticket JIRA ticket full name.
  * @param comment Comment to be placed in the ticket conversation.
  * @return {@code True} if ticket was succesfully commented. Otherwise - 
{@code false}.
  */
-boolean commentJiraTicket(String ticket, String comment);
+boolean sendJiraComment(String ticket, String comment);
 
 
 default void setAuthData(String user, String password) {
diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
index 1e10d78..7f17075 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
@@ -853,8 +853,8 @@ public void setExecutor(ExecutorService executor) {
 }
 
 /** {@inheritDoc} */
-@Override public boolean commentJiraTicket(String ticket, String comment) {
-return teamcity.commentJiraTicket(ticket, comment);
+@Override public boolean sendJiraComment(String ticket, String comment) {
+return teamcity.sendJiraComment(ticket, comment);
 }
 
 /** {@inheritDoc} */
diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
index 249a72a..f55222e 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
@@ -176,7 +176,7 @@ public IgniteTeamcityHelper(@Nullable String tcName) {
 }
 
 /** {@inheritDoc} */
-@Override public boolean commentJiraTicket(String ticket, String comment) {
+@Override public boolean sendJiraComment(String ticket, String comment) {
 try {
 String url = "https://issues.apache.org/jira/rest/api/2/issue/; + 
ticket + "/comment";
 
@@ -195,6 +195,7 @@ public IgniteTeamcityHelper(@Nullable String tcName) {
 @Override public PullRequest getPullRequest(String branchForTc) {
 String id = null;
 
+// Get PR id from string "pull//head"
 for (int i = 5; i < branchForTc.length(); i++) {
 char c = branchForTc.charAt(i);
 
diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
index a95483b..de0e7ea 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
@@ -20,16 +20,26 @@
 import com.google.common.base.Strings;
 import com.google.common.cache.Cache;
 import com.google.common.cache.CacheBuilder;
+import java.util.ArrayList;
+import java.util.LinkedHashMap;
 import java.util.List;
+import java.util.Map;
 import org.apache.ignite.Ignite;
 import org.apache.ignite.ci.conf.BranchesTracked;
 import org.apache.ignite.ci.observer.BuildObserver;
 import org.apache.ignite.ci.issue.IssueDetector;
 import org.apache.ignite.ci.issue.IssuesStorage;
+import 

[GitHub] ignite pull request #4625: IGNITE-9392 : Specified TX timeout in test config...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4625


---

[GitHub] SomeFire opened a new pull request #10: IGNITE-9588 Separate page for JIRA, GitHub actions

[GitBox]

SomeFire opened a new pull request #10: IGNITE-9588 Separate page for JIRA, 
GitHub actions
URL: https://github.com/apache/ignite-teamcity-bot/pull/10
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] ignite pull request #4718: IGNITE-9487 Introduce IGNITE_REST_GETALL_KEY_VALU...

[alamar]

Github user alamar closed the pull request at:

https://github.com/apache/ignite/pull/4718


---

[jira] [Created] (IGNITE-9605) Implicit mvcc transaction could use completed one instead of starting new

[Ivan Pavlukhin (JIRA)]

Ivan Pavlukhin created IGNITE-9605:
--

 Summary: Implicit mvcc transaction could use completed one instead 
of starting new
 Key: IGNITE-9605
 URL: https://issues.apache.org/jira/browse/IGNITE-9605
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Ivan Pavlukhin


It is possible that statement executed outside of explicit transaction uses 
completed one explicit transaction from ThreadLocal and fails.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9604) Implicit mvcc transaction could use completed one instead of starting new

[Ivan Pavlukhin (JIRA)]

Ivan Pavlukhin created IGNITE-9604:
--

 Summary: Implicit mvcc transaction could use completed one instead 
of starting new
 Key: IGNITE-9604
 URL: https://issues.apache.org/jira/browse/IGNITE-9604
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Ivan Pavlukhin


It is possible that statement executed outside of explicit transaction uses 
completed one explicit transaction from ThreadLocal and fails.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Apache Ignite 2.7 release

[Alexey Goncharuk]

We already have all the mechanics in place to work with properties - we use
ignite.build and ignite.revision from ignite.properties which are adjusted
during the build in the binary package.

Should I create the ticket if there are no objections?

пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev :

> Hello!
>
> So now there's an issue that this script makes source change after every
> build, show up in git status.
>
> What we could do to it:
> - Commit the changes after the build, once. In hopes that it won't change
> very often. With benefit that we could do that right now, before the code
> freeze.
> - Move these values to a properties file from both pom.xml and
> IgniteProvider.java. Any problems with this approach? We'll just read them
> from classpath properties file.
> - Update the links in the file once and remove them from build process. Why
> were they added to build process in the first place - to make them
> configurable during build?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 11 сент. 2018 г. в 5:53, Roman Shtykh :
>
> > Ilya,
> >
> > The "latest" version is the default, and resolved by
> > https://ignite.apache.org/latest which is used by our web site when a
> > user download the latest Ignite version. And I think this is the
> authority
> > to judge of the latest official release (pom.xml you suggest can have
> > SNAPSHOTs etc.).
> > Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> > driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> > version of Ignite he/she specifies. By default, it's "latest" but a user
> > can specify any version needed, even from a non-archive URL.
> >
> > In short, what we have now
> > 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> > -> it will try to resolve the latest officially releases version of
> Apache
> > Ignite, find the closest mirror and download Ignite in a minute. If the
> > version resolution fails, we fall back to the slow apache archive (as you
> > suggest; in my opinion we better fail-fast instead of waiting for hours
> to
> > download, so the user can choose another download option (3))
> > 2. If the user specifies the version explicitly, it goes to the slow
> > apache archive.
> > 3. The user can put ignite zip file on his/her http server and provide
> the
> > URL as a parameter to the driver, if options 1 and 2 don't work.
> >
> > As you see, there are 3 options. And I just fix the 1st one with
> > https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> > original logic (which I find reasonable) documented on our site -- I
> don't
> > see how it blocks anything.
> >
> > Roman Shtykh
> >
> >
> > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > There's still two issues with the submission.
> >
> > The first one is that we're downloading "latest" version from preferred
> > mirror but a specified version, such as "2.6", we're also going to
> download
> > from "slow" archive.apache.org/dist.
> > That's a great limitation for this change, since most real deployments of
> > Apache Ignite will have their Ignite version pegged to a specific
> release.
> > But in this case there's no win in download speed.
> > *In my opinion it is a blocker.*
> >
> > The second one is that we can't download anything when we failed to
> > resolve "latest". My idea is that we should try and download last known
> > version in this case, which can be pushed to source from pom.xml, as we
> > already do with URLs. So if you could not resolve "latest" you will
> > download 2.7.0.
> >
> > Buuut, maybe it's not necessary, maybe we should just *discourage
> > "latest"*, which is in my opinion almost always a bad idea.
> >
> > WDYT?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh :
> >
> > Hi Ilya,
> >
> > Sorry, missed that.
> > Added now.
> >
> > --
> > Roman Shtykh
> >
> >
> > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > The last of my requests still standing is that we should fall-back to
> > single URL download in case of error with 'latest' version. Everything
> else
> > looks good to me.
> >
> > Can we do that? I'm really worried that Apache API will go sour.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh :
> >
> > Hi Ilya,
> >
> > Thanks again.
> >
> > 1) Done.
> > 2) Used catch() for latest version.
> >
> > Please see my comments on github.
> > --
> > Roman Shtykh
> >
> >
> > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > I've left a new wave of replies.
> >
> > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> > that it will work even if build process is broken (would be useful for
> e.g.
> > developing 

[GitHub] ignite pull request #4760: Ignite 9585 experimental

[oignatenko]

Github user oignatenko closed the pull request at:

https://github.com/apache/ignite/pull/4760


---

Re: TeamCity permissions

[Nikita Amelchev]

Hi Dmitriy, Peter,

I have checked and now I can to cancel builds.

Thanks very much!
пт, 14 сент. 2018 г. в 18:05, Dmitriy Pavlov :
>
> Hi Nikita,
>
> I've checked permissions and it seems you can manage the queue.
>
> This makes me believe you can also cancel builds.
>
> Could you please double-check?
>
> I appreciate if other TC admins can advise me how to assign this role
> correctly.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 14 сент. 2018 г. в 17:12, Nikita Amelchev :
>
> > Hi, Igniters.
> >
> > I am working on MTCGA tasks and sometimes I need to cancel my builds.
> > It would be great if you grant permissions to stop builds to me.
> > My TC login: nsamelchev
> > ср, 23 мая 2018 г. в 17:36, Vitaliy Osipov :
> > >
> > > Hi.
> > >
> > > Done. Check please.
> > >
> > > On 23 May 2018 at 17:28, Maxim Muzafarov  wrote:
> > >
> > > > Hello, Igniters
> > > >
> > > > Would you be so pleased, also grant permissions to cancel builds on
> > > > TeamCity for me? I'm not iteresting to reorder builds.
> > > > Username: mmuzaf
> > > >
> > > >
> > > > пн, 21 мая 2018 г. в 19:32, Pavel Petroshenko :
> > > >
> > > >> It works, thanks Vitaliy!
> > > >>
> > > >> p.
> > > >>
> > > >> On Sun, May 20, 2018 at 1:16 PM, Vitaliy Osipov  > >
> > > >> wrote:
> > > >>
> > > >> > Pavel. Hi
> > > >> >
> > > >> > The necessary rights have been added. Check please.
> > > >> >
> > > >> > On 19 May 2018 at 01:48, Pavel Petroshenko 
> > > >> wrote:
> > > >> >
> > > >> >> Thank you, Denis! I need to have a role to be able to temporary
> > > >> rearrange
> > > >> >> builds in the TC build queue for testing and CI integration
> > purposes.
> > > >> >>
> > > >> >> Vitaly, I would appreciate any help.
> > > >> >>
> > > >> >> Thanks,
> > > >> >> P.
> > > >> >>
> > > >> >>
> > > >> >> On Fri, May 18, 2018 at 10:49 AM, Denis Magda 
> > > >> wrote:
> > > >> >>
> > > >> >>> Hi Pavel,
> > > >> >>>
> > > >> >>> All the accounts are assigned Project developer role on TC that
> > should
> > > >> >>> provide anything you need to manage builds there.
> > > >> >>>
> > > >> >>> What specifically are you looking for? Please elaborate so that
> > Vitaly
> > > >> >>> can
> > > >> >>> grant more permissions.
> > > >> >>>
> > > >> >>> Vitaly, please keep an eye on the conversation.
> > > >> >>>
> > > >> >>> --
> > > >> >>> Denis
> > > >> >>>
> > > >> >>>
> > > >> >>> On Fri, May 18, 2018 at 9:44 AM, Pavel Petroshenko <
> > > >> >>> pa...@petroshenko.com>
> > > >> >>> wrote:
> > > >> >>>
> > > >> >>> > Hi,
> > > >> >>> >
> > > >> >>> > Can anyone please grant TC permissions to manage jobs (reorder,
> > etc)
> > > >> >>> to:
> > > >> >>> >
> > > >> >>> > ekaterina.vergizova
> > > >> >>> > alexey.kosenchuk
> > > >> >>> > pavel.petroshenko
> > > >> >>> >
> > > >> >>> > Thanks!
> > > >> >>> > p.
> > > >> >>> >
> > > >> >>>
> > > >> >>
> > > >> >>
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Kind Regards
> > > >> > Vitaliy Osipov
> > > >> > vosi...@gridgain.com
> > > >> > *+7 (921) 397 27 68 <+7%20921%20397-27-68> <+7%20921%20397-27-68>*
> > > >> >
> > > >> > *gridgain.com *Powered by Apache® Ignite™
> > > >> >
> > > >>
> > > >
> > >
> > >
> > > --
> > > Kind Regards
> > > Vitaliy Osipov
> > > vosi...@gridgain.com
> > > *+7 (921) 397 27 68 <+7%20921%20397-27-68>*
> > >
> > > *gridgain.com *Powered by Apache® Ignite™
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >



-- 
Best wishes,
Amelchev Nikita

[GitHub] ignite pull request #4636: IGNITE-9398 Async notification to discovery spi l...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4636


---

Re: TeamCity permissions

[Dmitriy Pavlov]

Hi Nikita,

I've checked permissions and it seems you can manage the queue.

This makes me believe you can also cancel builds.

Could you please double-check?

I appreciate if other TC admins can advise me how to assign this role
correctly.

Sincerely,
Dmitriy Pavlov

пт, 14 сент. 2018 г. в 17:12, Nikita Amelchev :

> Hi, Igniters.
>
> I am working on MTCGA tasks and sometimes I need to cancel my builds.
> It would be great if you grant permissions to stop builds to me.
> My TC login: nsamelchev
> ср, 23 мая 2018 г. в 17:36, Vitaliy Osipov :
> >
> > Hi.
> >
> > Done. Check please.
> >
> > On 23 May 2018 at 17:28, Maxim Muzafarov  wrote:
> >
> > > Hello, Igniters
> > >
> > > Would you be so pleased, also grant permissions to cancel builds on
> > > TeamCity for me? I'm not iteresting to reorder builds.
> > > Username: mmuzaf
> > >
> > >
> > > пн, 21 мая 2018 г. в 19:32, Pavel Petroshenko :
> > >
> > >> It works, thanks Vitaliy!
> > >>
> > >> p.
> > >>
> > >> On Sun, May 20, 2018 at 1:16 PM, Vitaliy Osipov  >
> > >> wrote:
> > >>
> > >> > Pavel. Hi
> > >> >
> > >> > The necessary rights have been added. Check please.
> > >> >
> > >> > On 19 May 2018 at 01:48, Pavel Petroshenko 
> > >> wrote:
> > >> >
> > >> >> Thank you, Denis! I need to have a role to be able to temporary
> > >> rearrange
> > >> >> builds in the TC build queue for testing and CI integration
> purposes.
> > >> >>
> > >> >> Vitaly, I would appreciate any help.
> > >> >>
> > >> >> Thanks,
> > >> >> P.
> > >> >>
> > >> >>
> > >> >> On Fri, May 18, 2018 at 10:49 AM, Denis Magda 
> > >> wrote:
> > >> >>
> > >> >>> Hi Pavel,
> > >> >>>
> > >> >>> All the accounts are assigned Project developer role on TC that
> should
> > >> >>> provide anything you need to manage builds there.
> > >> >>>
> > >> >>> What specifically are you looking for? Please elaborate so that
> Vitaly
> > >> >>> can
> > >> >>> grant more permissions.
> > >> >>>
> > >> >>> Vitaly, please keep an eye on the conversation.
> > >> >>>
> > >> >>> --
> > >> >>> Denis
> > >> >>>
> > >> >>>
> > >> >>> On Fri, May 18, 2018 at 9:44 AM, Pavel Petroshenko <
> > >> >>> pa...@petroshenko.com>
> > >> >>> wrote:
> > >> >>>
> > >> >>> > Hi,
> > >> >>> >
> > >> >>> > Can anyone please grant TC permissions to manage jobs (reorder,
> etc)
> > >> >>> to:
> > >> >>> >
> > >> >>> > ekaterina.vergizova
> > >> >>> > alexey.kosenchuk
> > >> >>> > pavel.petroshenko
> > >> >>> >
> > >> >>> > Thanks!
> > >> >>> > p.
> > >> >>> >
> > >> >>>
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Kind Regards
> > >> > Vitaliy Osipov
> > >> > vosi...@gridgain.com
> > >> > *+7 (921) 397 27 68 <+7%20921%20397-27-68> <+7%20921%20397-27-68>*
> > >> >
> > >> > *gridgain.com *Powered by Apache® Ignite™
> > >> >
> > >>
> > >
> >
> >
> > --
> > Kind Regards
> > Vitaliy Osipov
> > vosi...@gridgain.com
> > *+7 (921) 397 27 68 <+7%20921%20397-27-68>*
> >
> > *gridgain.com *Powered by Apache® Ignite™
>
>
>
> --
> Best wishes,
> Amelchev Nikita
>

Re: TeamCity Helper shows new failures in PRs

[Dmitriy Pavlov]

Hi Ivan,

Actually, I don't know why it is impossible to accept. It is the first time
I send an invitation to the dev.list.

I've checked it and I have an error also. I've changed event visibility to
the public, but the result is the same.

So if you can see the event and its details, please join the meeting in
GoToMeeting. Accepting meeting is not paramount.

Sincerely,
Dmitriy Pavlov

пт, 14 сент. 2018 г. в 17:36, Павлухин Иван :

> Dmitry,
>
> I cannot confirm invitation. Do I need special permissions for
> dev@ignite.apache.org calendar?
>
> 2018-09-14 12:24 GMT+03:00 Dmitriy Pavlov :
>
> > Please see the invitation as a separate thread. Could you please also
> > confirm invitation came?
> >
> > пт, 14 сент. 2018 г. в 12:13, Павлухин Иван :
> >
> > > Hi guys!
> > >
> > > Webinar sounds as good idea. But could you please shortly describe the
> > main
> > > webinar theme? For those who are out of context =)
> > >
> > > 2018-09-14 10:33 GMT+03:00 Dmitrii Ryabov :
> > >
> > > > Hi, Dmitriy,
> > > >
> > > > Webinar is good, but we need a page on the wiki (or "help" in the
> bot)
> > > for
> > > > new contributors. After that, I think we should add mention about
> > helper
> > > to
> > > > the contributing guide.
> > > >
> > > > 2018-09-14 9:43 GMT+03:00 Nikolay Izhikov :
> > > >
> > > > > Hello, Dmitriy.
> > > > >
> > > > > Webinar is a great idea, let's have it.
> > > > >
> > > > > В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> > > > > > Hi Folks,
> > > > > >
> > > > > > There is no description of this feature yet. But I think we
> should
> > > come
> > > > > > back to the idea of running a webinar.
> > > > > >
> > > > > > Please share your vision. If Igniters will attend I send an
> > > invitation
> > > > to
> > > > > > the beginning of next week.
> > > > > >
> > > > > > I hope in the nearest time we will have a few more features to
> > speak
> > > > > about.
> > > > > >
> > > > > > Sincerely,
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov <
> nizhi...@apache.org
> > >:
> > > > > >
> > > > > > > Hello, Dmitrii.
> > > > > > >
> > > > > > > Can you give a link to detailed description of this feature?
> > > > > > >
> > > > > > > Actually, I wonder if someone except bit developers know how to
> > use
> > > > it
> > > > > > >
> > > > > > > чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov <
> > somefire...@gmail.com
> > > >:
> > > > > > >
> > > > > > > > Hello, Igniters!
> > > > > > > >
> > > > > > > > We've improved tests analysis in the TeamCity Helper.
> > > > > > > >
> > > > > > > > Now, when you view PR analysis, you can see a table with
> > possible
> > > > > > >
> > > > > > > blockers
> > > > > > > > - failed tests and suites, that most likely appeared in the
> > pull
> > > > > request.
> > > > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: TeamCity Helper shows new failures in PRs

[Павлухин Иван]

Dmitry,

I cannot confirm invitation. Do I need special permissions for
dev@ignite.apache.org calendar?

2018-09-14 12:24 GMT+03:00 Dmitriy Pavlov :

> Please see the invitation as a separate thread. Could you please also
> confirm invitation came?
>
> пт, 14 сент. 2018 г. в 12:13, Павлухин Иван :
>
> > Hi guys!
> >
> > Webinar sounds as good idea. But could you please shortly describe the
> main
> > webinar theme? For those who are out of context =)
> >
> > 2018-09-14 10:33 GMT+03:00 Dmitrii Ryabov :
> >
> > > Hi, Dmitriy,
> > >
> > > Webinar is good, but we need a page on the wiki (or "help" in the bot)
> > for
> > > new contributors. After that, I think we should add mention about
> helper
> > to
> > > the contributing guide.
> > >
> > > 2018-09-14 9:43 GMT+03:00 Nikolay Izhikov :
> > >
> > > > Hello, Dmitriy.
> > > >
> > > > Webinar is a great idea, let's have it.
> > > >
> > > > В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> > > > > Hi Folks,
> > > > >
> > > > > There is no description of this feature yet. But I think we should
> > come
> > > > > back to the idea of running a webinar.
> > > > >
> > > > > Please share your vision. If Igniters will attend I send an
> > invitation
> > > to
> > > > > the beginning of next week.
> > > > >
> > > > > I hope in the nearest time we will have a few more features to
> speak
> > > > about.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov  >:
> > > > >
> > > > > > Hello, Dmitrii.
> > > > > >
> > > > > > Can you give a link to detailed description of this feature?
> > > > > >
> > > > > > Actually, I wonder if someone except bit developers know how to
> use
> > > it
> > > > > >
> > > > > > чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov <
> somefire...@gmail.com
> > >:
> > > > > >
> > > > > > > Hello, Igniters!
> > > > > > >
> > > > > > > We've improved tests analysis in the TeamCity Helper.
> > > > > > >
> > > > > > > Now, when you view PR analysis, you can see a table with
> possible
> > > > > >
> > > > > > blockers
> > > > > > > - failed tests and suites, that most likely appeared in the
> pull
> > > > request.
> > > > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>



-- 
Best regards,
Ivan Pavlukhin

[jira] [Created] (IGNITE-9603) Cache proxy flags are not (de)serialized

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-9603:


 Summary: Cache proxy flags are not (de)serialized
 Key: IGNITE-9603
 URL: https://issues.apache.org/jira/browse/IGNITE-9603
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Goncharuk


The following code will fail with {{ClassNotFoundException}} assuming that 
cache contains a complex object with key {{1}}.

IgniteCache cache = ignite.cache(CACHE_NAME).withKeepBinary();

ignite.compute().broadcast(() -> {
cache.get(1);
});

The {{withKeepBinary()}} flag is not serialized into the closure and causes the 
{{cache.get(1)}} to attempt to deserialize cache read result.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: TeamCity permissions

[Nikita Amelchev]

Hi, Igniters.

I am working on MTCGA tasks and sometimes I need to cancel my builds.
It would be great if you grant permissions to stop builds to me.
My TC login: nsamelchev
ср, 23 мая 2018 г. в 17:36, Vitaliy Osipov :
>
> Hi.
>
> Done. Check please.
>
> On 23 May 2018 at 17:28, Maxim Muzafarov  wrote:
>
> > Hello, Igniters
> >
> > Would you be so pleased, also grant permissions to cancel builds on
> > TeamCity for me? I'm not iteresting to reorder builds.
> > Username: mmuzaf
> >
> >
> > пн, 21 мая 2018 г. в 19:32, Pavel Petroshenko :
> >
> >> It works, thanks Vitaliy!
> >>
> >> p.
> >>
> >> On Sun, May 20, 2018 at 1:16 PM, Vitaliy Osipov 
> >> wrote:
> >>
> >> > Pavel. Hi
> >> >
> >> > The necessary rights have been added. Check please.
> >> >
> >> > On 19 May 2018 at 01:48, Pavel Petroshenko 
> >> wrote:
> >> >
> >> >> Thank you, Denis! I need to have a role to be able to temporary
> >> rearrange
> >> >> builds in the TC build queue for testing and CI integration purposes.
> >> >>
> >> >> Vitaly, I would appreciate any help.
> >> >>
> >> >> Thanks,
> >> >> P.
> >> >>
> >> >>
> >> >> On Fri, May 18, 2018 at 10:49 AM, Denis Magda 
> >> wrote:
> >> >>
> >> >>> Hi Pavel,
> >> >>>
> >> >>> All the accounts are assigned Project developer role on TC that should
> >> >>> provide anything you need to manage builds there.
> >> >>>
> >> >>> What specifically are you looking for? Please elaborate so that Vitaly
> >> >>> can
> >> >>> grant more permissions.
> >> >>>
> >> >>> Vitaly, please keep an eye on the conversation.
> >> >>>
> >> >>> --
> >> >>> Denis
> >> >>>
> >> >>>
> >> >>> On Fri, May 18, 2018 at 9:44 AM, Pavel Petroshenko <
> >> >>> pa...@petroshenko.com>
> >> >>> wrote:
> >> >>>
> >> >>> > Hi,
> >> >>> >
> >> >>> > Can anyone please grant TC permissions to manage jobs (reorder, etc)
> >> >>> to:
> >> >>> >
> >> >>> > ekaterina.vergizova
> >> >>> > alexey.kosenchuk
> >> >>> > pavel.petroshenko
> >> >>> >
> >> >>> > Thanks!
> >> >>> > p.
> >> >>> >
> >> >>>
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Kind Regards
> >> > Vitaliy Osipov
> >> > vosi...@gridgain.com
> >> > *+7 (921) 397 27 68 <+7%20921%20397-27-68>*
> >> >
> >> > *gridgain.com *Powered by Apache® Ignite™
> >> >
> >>
> >
>
>
> --
> Kind Regards
> Vitaliy Osipov
> vosi...@gridgain.com
> *+7 (921) 397 27 68*
>
> *gridgain.com *Powered by Apache® Ignite™



-- 
Best wishes,
Amelchev Nikita

[GitHub] ignite pull request #4763: Ignite 9599 mx bean

[a-polyakov]

GitHub user a-polyakov opened a pull request:

https://github.com/apache/ignite/pull/4763

Ignite 9599 mx bean



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite IGNITE-9599_MXBean

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4763.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4763


commit 86accac5b9db0e08a65ca61f4fbc7f26fcd326be
Author: a-polyakov 
Date:   2018-09-14T10:38:50Z

IGNITE-9599 Add ability to manage compression level for compressed WAL 
archives

Signed-off-by: a-polyakov 

commit a60e270e4e3ad84ef0d7d8150c19367d7a562ba3
Author: a-polyakov 
Date:   2018-09-14T13:59:21Z

IGNITE-9599 MXBean control level for compressed WAL archives

Signed-off-by: a-polyakov 




---

[jira] [Created] (IGNITE-9602) Transaction timeout setter could break GridTimeoutProcessor behavior

[Ivan Pavlukhin (JIRA)]

Ivan Pavlukhin created IGNITE-9602:
--

 Summary: Transaction timeout setter could break 
GridTimeoutProcessor behavior
 Key: IGNITE-9602
 URL: https://issues.apache.org/jira/browse/IGNITE-9602
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.7
Reporter: Ivan Pavlukhin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4762: IGNITE-9601 Writing rollover record to the end of...

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

https://github.com/apache/ignite/pull/4762

IGNITE-9601 Writing rollover record to the end of current segment.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-9601

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4762.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4762


commit 13a1dfea64e5974f0014930a08bcf58d239f0428
Author: Andrey Kuznetsov 
Date:   2018-09-14T12:50:47Z

IGNITE-9601 Writing rollover record to the end of current segment.




---

[GitHub] ignite pull request #4761: IGNITE-9558

[ilantukh]

GitHub user ilantukh opened a pull request:

https://github.com/apache/ignite/pull/4761

IGNITE-9558



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9558

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4761.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4761


commit b1a17a82619b72c73453541ba2b85ac77a224050
Author: Ilya Lantukh 
Date:   2018-09-14T12:48:35Z

IGNITE-9558 : Assert for externalizable methods in ATV.




---

[GitHub] ignite pull request #4428: IGNITE-9074: Fixed ODBC error message on handshak...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4428


---

[GitHub] ignite pull request #4760: Ignite 9585 experimental

[oignatenko]

GitHub user oignatenko opened a pull request:

https://github.com/apache/ignite/pull/4760

Ignite 9585 experimental

temporary branch and PR for experimenting for Teamcity 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite 
ignite-9585-experimental

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4760.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4760


commit 1eeca908a8076a8317947dac8a46845964d1d7ea
Author: Oleg Ignatenko 
Date:   2018-08-23T13:13:28Z

IGNITE-9348 ML examples improvements
- wip (logging improved)
-- verified with diffs overview, executing the examples and studying 
execution logs

commit e50b89c392568ba9b93935c4fa6c7f7f93f5ec6f
Author: Oleg Ignatenko 
Date:   2018-08-23T14:45:57Z

Revert "IGNITE-9348 ML examples improvements"

This reverts commit 1eeca908a8076a8317947dac8a46845964d1d7ea.

commit 474024b4c5bbdb3c0a4ed2f0a66238c8054c6674
Author: Oleg Ignatenko 
Date:   2018-08-23T14:57:34Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9642b233b5701bdad47ebea163079160227c582a
Author: Oleg Ignatenko 
Date:   2018-08-28T14:01:11Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 7fc16d013ab725d2ff2e1a1b042c983f11d0c4d4
Author: Oleg Ignatenko 
Date:   2018-08-28T15:13:02Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit d2caba67b156674f051f50faebeafe0871bf0914
Author: Oleg Ignatenko 
Date:   2018-08-29T13:14:07Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 16775dff51d71ea68b4a3dea98be552130c493ed
Author: Oleg Ignatenko 
Date:   2018-08-30T09:00:56Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit aedb59929974fe205b949225c1a338c68c60cfc8
Author: Oleg Ignatenko 
Date:   2018-08-30T09:42:38Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 39c6482fcdca506aa33011ed21c98060b4a8c68b
Author: Oleg Ignatenko 
Date:   2018-08-30T11:28:05Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 33b32a2760a6559c78283b927e3191180d8ed9e1
Author: Oleg Ignatenko 
Date:   2018-08-30T12:31:16Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9531028ddd1aef9e95f7e8c8b528086739bbb1b0
Author: Oleg Ignatenko 
Date:   2018-08-30T14:06:34Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 28f22c6e2fffcb82717ba5da7be2cfd39715c4e3
Author: Oleg Ignatenko 
Date:   2018-08-30T16:41:51Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit aacac88db519187413b0fc5ff9d0e55b8f8cff22
Author: Oleg Ignatenko 
Date:   2018-08-31T10:12:32Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 897f920dde46022849b13f9fb86dba8e54119a56
Author: Oleg Ignatenko 
Date:   2018-08-31T13:57:14Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 114c79e54c1b316006ccc3ff22d20d902f9313df
Author: Oleg Ignatenko 
Date:   2018-08-31T17:39:16Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit fd6b659bb8be1992618ce4ce91f568a0988b3afa
Author: Oleg Ignatenko 
Date:   2018-09-02T06:11:42Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 6ae6d1d3cf9743d8d466be0330511ddc8589e944
Author: Oleg Ignatenko 
Date:   2018-09-03T10:27:35Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit e8b27dbd3d0c1cbdb7a7659175f5c7bb447482bf
Author: Oleg Ignatenko 
Date:   2018-09-04T09:49:44Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 622c82efdd0aa182fadea6b7ffa5d4615521a3f5
Author: Oleg Ignatenko 
Date:   2018-09-05T10:50:28Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit fb844fe3751e2e8ae87e6b8030b0e4bd659df9c2
Author: Oleg Ignatenko 
Date:   2018-09-05T11:45:58Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 480ed78869277d7e32f725ab71bec9621f1ac03a
Author: Oleg Ignatenko 
Date:   2018-09-06T07:52:55Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit c99762498f617c0e98ea3062a43c0b30092166ef
Author: Oleg Ignatenko 
Date:   2018-09-06T14:45:04Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 2e17175225c72f747d370b5fee96f8be69d6d2cb
Author: Oleg Ignatenko 
Date:   2018-09-06T17:33:54Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9ebcd9a2fe5966b0bf42a95484395867c15d863f
Author: Oleg Ignatenko 
Date:   2018-09-07T13:38:51Z

Merge 

[jira] [Created] (IGNITE-9601) Write rollover WAL record as the last

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-9601:


 Summary: Write rollover WAL record as the last 
 Key: IGNITE-9601
 URL: https://issues.apache.org/jira/browse/IGNITE-9601
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.6
Reporter: Andrey Kuznetsov
Assignee: Andrey Kuznetsov
 Fix For: 2.8


Currently, rollover WAL record gets to the next segment when being logged. 
Moreover, the implementation does allows data races, and rollover record is not 
necessarily the first record in the next segment. We are to add an option to 
logging facility to allow writing rollover record to the end of the current 
segment; subsequent records should get to the next segment then.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Python thin client

[Igor Sapego]

Ok, good.

Now, what is about installation? Which directories/files
need to be copied to ignite's binary release?

Best Regards,
Igor


On Fri, Sep 14, 2018 at 4:51 AM Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Igor,
>
> The commented code (lines 95-96) gives an error if executed. The error
> is stated just below, in lines 98-100. It is explained here:
>
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#create
>
> I found out by trial and error that a cache, created with SQL DDL
> statement (`CREATE TABLE`), can be deleted only with SQL DDL statement
> (`DROP TABLE`), whereas a table, created with a binary protocol
> operation (`OP_CACHE_CREATE_*` or `OP_CACHE_GET_OR_CREATE_*`) can be
> deleted only with binary protocol operation (`OP_CACHE_DESTROY`). I miss
> this fact in Ignite documentation.
>
> In this particular part of the example I try to stress this out with
> regard to the cache created in the beginning of the example. The cache
> behaves like an SQL table, but can not be dropped. You need to destroy
> it instead (line 102).
>
> I would not go into such depths at all, but the examples are designed to
> be runnable in automated environments, and thus must have some cleanup
> code. And since the cleanup here is not absolutely trivial, I thought I
> must explain it.
>
> I also could handle an error instead of commenting the erroneous code, like
>
> ```
> any_error = None
> try:
>  DROP_QUERY = 'DROP TABLE Student'
>  client.sql(DROP_QUERY)
> except Exception as e:
>  any_error = e
> print(any_error)
>
> # pyignite.exceptions.SQLError: class
> org.apache.ignite.IgniteCheckedException:
> # Only cache created with CREATE TABLE may be removed with DROP TABLE
> # [cacheName=SQL_PUBLIC_STUDENT]
>
> but it would complicate the cleanup part of the example to the point it
> is lost any exemplariness. So I decided to simply use comments.
>
> On 9/14/18 2:48 AM, Igor Sapego wrote:
> > Ok, now everything's running.
> >
> > API looks good to me. I have a single question about example code:
> > What these comments are for - [1]?
> >
> > [1] -
> >
> https://github.com/nobitlost/ignite/blob/ignite-7782/modules/platforms/python/examples/create_binary.py#L95
> >
> > Best Regards,
> > Igor
> >
> >
> > On Thu, Sep 13, 2018 at 12:52 AM Dmitry Melnichuk <
> > dmitry.melnic...@nobitlost.com> wrote:
> >
> >> Igor,
> >>
> >> Yes, it's my bad, sorry. Just merged the Ignite master with my branch.
> >>
> >> On 9/12/18 8:47 PM, Igor Sapego wrote:
> >>> Pavel,
> >>> Yes, I did. I tried completely clean environment, followed the same
> >>> steps and got the same error. Then I removed attr, and out of sudden
> >>> everything started working.
> >>>
> >>> Dmitry,
> >>> Thanks, now it's more clear:
> >>> Handshake error: Unsupported version. Server expects binary protocol
> >>> version 1.1.0. Client provides 1.2.0.
> >>>
> >>> Why do you use version 1.2.0, but have outdated server code? I
> >>> propose you to merge with or rebase onto Ignite's master branch.
> >>>
> >>> Best Regards,
> >>> Igor
> >>>
> >>>
> >>> On Tue, Sep 11, 2018 at 11:21 PM Dmitry Melnichuk <
> >>> dmitry.melnic...@nobitlost.com> wrote:
> >>>
>  Igor,
> 
>  I have just commited an improvment to the HandshakeError message
>  generation algorithm. I hope it is now easier to understand what
> expects
>  what in case of binary protocol version mismatch.
> 
>  Thank you for pointing this out.
> 
>  On 9/12/18 2:13 AM, Igor Sapego wrote:
> > I managed to start tests, and now I'm getting the following message:
> >
> > pyignite.exceptions.HandshakeError: Handshake error: Unsupported
> > version. Expected protocol version: 1.1.0.
> >
> > It would be useful to print "Unexpected version" itself, because I
> can
> > not understand what is the issue.
> >
> > Best Regards,
> > Igor
> 
> >>>
> >>
> >>
> >
>
>

[GitHub] ignite pull request #4759: IGNITE-9599 Add ability to manage compression lev...

[a-polyakov]

GitHub user a-polyakov opened a pull request:

https://github.com/apache/ignite/pull/4759

IGNITE-9599 Add ability to manage compression level for compressed WAL 
archives



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite IGNITE-9599

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4759.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4759


commit 73b2170fe87595be35bce4cea74c6f86729e2ad7
Author: a-polyakov 
Date:   2018-09-14T10:38:50Z

IGNITE-9599 Add ability to manage compression level for compressed WAL 
archives

Signed-off-by: a-polyakov 




---

[GitHub] ignite pull request #4757: IGNITE-9593: Fix of IgniteOptimization bugs.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4757


---

Re: Apache Ignite 2.7 release

[Ilya Kasnacheev]

Hello!

So now there's an issue that this script makes source change after every
build, show up in git status.

What we could do to it:
- Commit the changes after the build, once. In hopes that it won't change
very often. With benefit that we could do that right now, before the code
freeze.
- Move these values to a properties file from both pom.xml and
IgniteProvider.java. Any problems with this approach? We'll just read them
from classpath properties file.
- Update the links in the file once and remove them from build process. Why
were they added to build process in the first place - to make them
configurable during build?

Regards,
-- 
Ilya Kasnacheev


вт, 11 сент. 2018 г. в 5:53, Roman Shtykh :

> Ilya,
>
> The "latest" version is the default, and resolved by
> https://ignite.apache.org/latest which is used by our web site when a
> user download the latest Ignite version. And I think this is the authority
> to judge of the latest official release (pom.xml you suggest can have
> SNAPSHOTs etc.).
> Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> version of Ignite he/she specifies. By default, it's "latest" but a user
> can specify any version needed, even from a non-archive URL.
>
> In short, what we have now
> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> -> it will try to resolve the latest officially releases version of Apache
> Ignite, find the closest mirror and download Ignite in a minute. If the
> version resolution fails, we fall back to the slow apache archive (as you
> suggest; in my opinion we better fail-fast instead of waiting for hours to
> download, so the user can choose another download option (3))
> 2. If the user specifies the version explicitly, it goes to the slow
> apache archive.
> 3. The user can put ignite zip file on his/her http server and provide the
> URL as a parameter to the driver, if options 1 and 2 don't work.
>
> As you see, there are 3 options. And I just fix the 1st one with
> https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> original logic (which I find reasonable) documented on our site -- I don't
> see how it blocks anything.
>
> Roman Shtykh
>
>
> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>
> Hello!
>
> There's still two issues with the submission.
>
> The first one is that we're downloading "latest" version from preferred
> mirror but a specified version, such as "2.6", we're also going to download
> from "slow" archive.apache.org/dist.
> That's a great limitation for this change, since most real deployments of
> Apache Ignite will have their Ignite version pegged to a specific release.
> But in this case there's no win in download speed.
> *In my opinion it is a blocker.*
>
> The second one is that we can't download anything when we failed to
> resolve "latest". My idea is that we should try and download last known
> version in this case, which can be pushed to source from pom.xml, as we
> already do with URLs. So if you could not resolve "latest" you will
> download 2.7.0.
>
> Buuut, maybe it's not necessary, maybe we should just *discourage
> "latest"*, which is in my opinion almost always a bad idea.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh :
>
> Hi Ilya,
>
> Sorry, missed that.
> Added now.
>
> --
> Roman Shtykh
>
>
> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>
> Hello!
>
> The last of my requests still standing is that we should fall-back to
> single URL download in case of error with 'latest' version. Everything else
> looks good to me.
>
> Can we do that? I'm really worried that Apache API will go sour.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh :
>
> Hi Ilya,
>
> Thanks again.
>
> 1) Done.
> 2) Used catch() for latest version.
>
> Please see my comments on github.
> --
> Roman Shtykh
>
>
> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>
> Hello!
>
> I've left a new wave of replies.
>
> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> that it will work even if build process is broken (would be useful for e.g.
> developing out of IDE)
> And also I urge you to catch() around new fragile Apache JSON API
> resolving, and download the 'current' version instead, as defined by
> ignite-mesos version.
>
> This is because this module is not under continuouos scrutiny so extra
> care should be applied.
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh :
>
> Thanks, Ilya!
> I will check your comments, and discuss it at JIRA.
>
> --
> Roman Shtykh
>
>
> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>
> Hello!
>
> IGNITE-9408 

[GitHub] ignite pull request #4758: IGNITE-9597: replace with isEmpty

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

https://github.com/apache/ignite/pull/4758

IGNITE-9597: replace with isEmpty



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Mmuzaf/ignite ignite-9597

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4758.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4758


commit a180e18e0f2a898afeb076d771c9a642b2c6b2bd
Author: Maxim Muzafarov 
Date:   2018-09-14T09:56:47Z

IGNITE-9597: replace with isEmpty




---

[GitHub] ignite pull request #4757: IGNITE-9593: Fix of IgniteOptimization bugs.

[nizhikov]

GitHub user nizhikov opened a pull request:

https://github.com/apache/ignite/pull/4757

IGNITE-9593: Fix of IgniteOptimization bugs.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nizhikov/ignite IGNITE-9593

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4757.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4757


commit e1800978d36115419be777dacbc79cc0e2e7c89a
Author: Nikolay Izhikov 
Date:   2018-09-14T04:06:48Z

IGNITE-9593: Two of three bugs fixed

commit 12791876fb421e2c81c1430c2e9fd5e3ec4a2185
Author: Nikolay Izhikov 
Date:   2018-09-14T09:45:15Z

IGNITE-9593: Fix of IgniteOptimization bugs.




---

[jira] [Created] (IGNITE-9600) SQL update fails if the sql updates more than one field

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-9600:
-

 Summary: SQL update fails if the sql updates more than one field
 Key: IGNITE-9600
 URL: https://issues.apache.org/jira/browse/IGNITE-9600
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.6
Reporter: Mikhail Cherkasov


SQL update fails if the sql updates more than one field:
{noformat}
Exception in thread "main" javax.cache.CacheException: Failed to execute map 
query on remote node [nodeId=9c46dc49-30d2-46ca-a2ec-8b1be7f19c91, 
errMsg=Failed to execute SQL query. Data conversion error converting "Entity2"; 
SQL statement:
SELECT
__Z0._KEY __C0_0,
__Z0._VAL __C0_1,
((?1 AND (__Z0.ENTITY_NAME2 = ?2)) AND (__Z0.CONTINENT = ?3)) __C0_2
FROM PUBLIC.ENTITY_TABLE __Z0
WHERE __Z0.ENTITY_ID = ?4 [22018-195]]
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:288)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:278)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:257)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:202)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2349)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748){noformat}
Looks like ignite or underlying h2 engine generates query incorrectly:

((?1 AND (__Z0.ENTITY_NAME2 = ?2)) AND (__Z0.CONTINENT = ?3)) __C0_2

the name for first field is missed.

 

The reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: TeamCity Helper shows new failures in PRs

[Dmitriy Pavlov]

Please see the invitation as a separate thread. Could you please also
confirm invitation came?

пт, 14 сент. 2018 г. в 12:13, Павлухин Иван :

> Hi guys!
>
> Webinar sounds as good idea. But could you please shortly describe the main
> webinar theme? For those who are out of context =)
>
> 2018-09-14 10:33 GMT+03:00 Dmitrii Ryabov :
>
> > Hi, Dmitriy,
> >
> > Webinar is good, but we need a page on the wiki (or "help" in the bot)
> for
> > new contributors. After that, I think we should add mention about helper
> to
> > the contributing guide.
> >
> > 2018-09-14 9:43 GMT+03:00 Nikolay Izhikov :
> >
> > > Hello, Dmitriy.
> > >
> > > Webinar is a great idea, let's have it.
> > >
> > > В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> > > > Hi Folks,
> > > >
> > > > There is no description of this feature yet. But I think we should
> come
> > > > back to the idea of running a webinar.
> > > >
> > > > Please share your vision. If Igniters will attend I send an
> invitation
> > to
> > > > the beginning of next week.
> > > >
> > > > I hope in the nearest time we will have a few more features to speak
> > > about.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov :
> > > >
> > > > > Hello, Dmitrii.
> > > > >
> > > > > Can you give a link to detailed description of this feature?
> > > > >
> > > > > Actually, I wonder if someone except bit developers know how to use
> > it
> > > > >
> > > > > чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov  >:
> > > > >
> > > > > > Hello, Igniters!
> > > > > >
> > > > > > We've improved tests analysis in the TeamCity Helper.
> > > > > >
> > > > > > Now, when you view PR analysis, you can see a table with possible
> > > > >
> > > > > blockers
> > > > > > - failed tests and suites, that most likely appeared in the pull
> > > request.
> > > > > >
> > >
> >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

[GitHub] ignite pull request #4756: IGNITE-9487 Introduce IGNITE_REST_GETALL_KEY_VALU...

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/4756

IGNITE-9487 Introduce IGNITE_REST_GETALL_KEY_VALUE to change getall output 
format.

Second take

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9487bis

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4756.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4756


commit b1b9ee2c32357f8919379e9b2d1606196eb42999
Author: Ilya Kasnacheev 
Date:   2018-09-14T09:21:29Z

IGNITE-9487 Introduce IGNITE_REST_GETALL_KEY_VALUE to change getall output 
format.




---

Приглашение: Apache Ignite TeamCity Bot: Features overview - вт, 18 сент 2018 17:00 - 18:00 (MSK) (dev@ignite.apache.org)

[Dmitriy Pavlov]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180918T14Z
DTEND:20180918T15Z
DTSTAMP:20180914T092359Z
ORGANIZER;CN=Dmitriy Pavlov:mailto:dpavlov@gmail.com
UID:2dm8hva8m323mg63ukrfuje...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@ignite.apache.org;X-NUM-GUESTS=0:mailto:dev@ignite.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Dmitriy Pavlov;X-NUM-GUESTS=0:mailto:dpavlov@gmail.com
CREATED:20180914T092358Z
DESCRIPTION:\nMost of you have noticed emails from the Bot to d...@ignite.ap
 ache.org. \n\nWe will cover details and features of this new monitoring and
  PR checking tool https://mtcga.gridgain.com/\n\n- We will know how test fa
 ilure is considered as a blocker by the bot.\n- When emails will appear on 
 the dev list and how to avoid it.\n- On this webinar we will cover major im
 plemented and some planned features.\n\nThe meeting is intended for Apache 
 Ignite Developers\, TC Bot enthusiasts and everyone interested.\n\n\nTue\, 
 Sep 18\, 2018 5:00 PM - 5:30 PM MSK \n\nPlease join my meeting from your co
 mputer\, tablet or smartphone. \nhttps://global.gotomeeting.com/join/364140
 429 \n\nYou can also dial in using your phone. \nUnited States: +1 (669) 22
 4-3412 \n\nAccess Code: 364-140-429 \n\nFirst GoToMeeting? Let's do a quick
  system check: \nhttps://link.gotomeeting.com/system-check \n\n-::~:~::~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
 \nНе редактируйте этот раздел описания.\n\nПросмотрите свое мероприятие на 
 странице https://www.google.com/calendar/event?action=VIEW=MmRtOGh2YTht
 MzIzbWc2M3VrcmZ1amV0aWYgZGV2QGlnbml0ZS5hcGFjaGUub3Jn=MjEjZHBhdmxvdi5zcG
 JAZ21haWwuY29tY2Y4MzIwZjE0ZWZiMTY0ZDA2Yzk2MTMxMzcwZGU3ZmZjN2M5YWQzMw=Eu
 rope%2FMoscow=ru=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180914T092358Z
LOCATION:https://global.gotomeeting.com/join/364140429 
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Apache Ignite TeamCity Bot: Features overview 
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H30M0S
END:VALARM
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H10M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

[jira] [Created] (IGNITE-9599) Add ability to manage compression level for compressed WAL archives

[Andrey Kalinin (JIRA)]

Andrey Kalinin created IGNITE-9599:
--

 Summary: Add ability to manage compression level for compressed 
WAL archives
 Key: IGNITE-9599
 URL: https://issues.apache.org/jira/browse/IGNITE-9599
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Kalinin


In some cases, WAL compression performance is not sufficient, i.e. new archives 
accumulate faster than old ones are compressed. We must add an option to change 
the default compression level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: TeamCity Helper shows new failures in PRs

[Павлухин Иван]

Hi guys!

Webinar sounds as good idea. But could you please shortly describe the main
webinar theme? For those who are out of context =)

2018-09-14 10:33 GMT+03:00 Dmitrii Ryabov :

> Hi, Dmitriy,
>
> Webinar is good, but we need a page on the wiki (or "help" in the bot) for
> new contributors. After that, I think we should add mention about helper to
> the contributing guide.
>
> 2018-09-14 9:43 GMT+03:00 Nikolay Izhikov :
>
> > Hello, Dmitriy.
> >
> > Webinar is a great idea, let's have it.
> >
> > В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> > > Hi Folks,
> > >
> > > There is no description of this feature yet. But I think we should come
> > > back to the idea of running a webinar.
> > >
> > > Please share your vision. If Igniters will attend I send an invitation
> to
> > > the beginning of next week.
> > >
> > > I hope in the nearest time we will have a few more features to speak
> > about.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov :
> > >
> > > > Hello, Dmitrii.
> > > >
> > > > Can you give a link to detailed description of this feature?
> > > >
> > > > Actually, I wonder if someone except bit developers know how to use
> it
> > > >
> > > > чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov :
> > > >
> > > > > Hello, Igniters!
> > > > >
> > > > > We've improved tests analysis in the TeamCity Helper.
> > > > >
> > > > > Now, when you view PR analysis, you can see a table with possible
> > > >
> > > > blockers
> > > > > - failed tests and suites, that most likely appeared in the pull
> > request.
> > > > >
> >
>



-- 
Best regards,
Ivan Pavlukhin

Re: [ML] [New Feature] Trainers as pipeline parameters that can be varied

[dmitrievanthony]

In case HTML doesn't work I'll duplicate the message.

Hi all,

A machine learning pipeline implemented in
https://issues.apache.org/jira/browse/IGNITE-9158 (see discussion  here
http://apache-ignite-developers.2346864.n4.nabble.com/ML-Machine-Learning-Pipeline-Improvement-tt32772.html)
supports hyperparameters variation, but not trainers variation so far.

Our  reference-framework scikit-learn (according to  documentation
http://scikit-learn.org/stable/modules/pipeline.html#pipeline) allows to
variate trainers and preprocessors the following way:

>>> param_grid = dict(reduce_dim=[None, PCA(5), PCA(10)],
...   clf=[SVC(), LogisticRegression()],
...   clf__C=[0.1, 10, 100])
>>> grid_search = GridSearchCV(pipe, param_grid=param_grid)

I think it would be a great improvement for our ML pipeline.

Alexey Zinoviev, it would be awesome if you as an author of original ML
pipeline take a look at this proposal. 



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4755: IGNITE-9573 Fix ZooKeeper SASL authentication tes...

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/4755

IGNITE-9573 Fix ZooKeeper SASL authentication tests.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9573

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4755.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4755


commit bd146cb9bb0459021a3f46fb3f1f5961118c32e8
Author: Ilya Kasnacheev 
Date:   2018-09-13T12:16:26Z

IGNITE-9573 Fix ZooKeeper SASL authentication tests.




---

[ML] [New Feature] Trainers as pipeline parameters that can be varied

[dmitrievanthony]

Hi all,A machine learning pipeline implemented in  IGNITE-9158
   (see discussion  here

 
) supports hyperparameters variation, but not trainers variation so far.Our
reference-framework scikit-learn (according to  documentation
  ) allows to
variate trainers and preprocessors the following way:>>> param_grid =
dict(reduce_dim=[None, PCA(5),
PCA(10)],...clf=[SVC(),
LogisticRegression()],...clf__C=[0.1,
10, 100])>>> grid_search = GridSearchCV(pipe, param_grid=param_grid)I think
it would be a great improvement for our ML pipeline.Alexey Zinoviev, it
would be awesome if you as an author of original ML pipeline take a look at
this proposal.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-9598) Error in console if user goes away from queries

[Alexander Kalinin (JIRA)]

Alexander Kalinin created IGNITE-9598:
-

 Summary: Error in console if user goes away from queries
 Key: IGNITE-9598
 URL: https://issues.apache.org/jira/browse/IGNITE-9598
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Alexander Kalinin
Assignee: Alexander Kalinin


If startWatch cluster function operates too long and user goes aways from 
queries the following error is raised in console:


{code:java}
Cannot read property 'unsubscribe' of undefined
at NotebookCtrl.$onDestroy (controller.js:1972)
at callOnDestroyHook (angular.js:10068)
at Scope.$broadcast (angular.js:19165)
at Scope.$destroy (angular.js:18779)
at cleanupLastView (ui-router-angularjs.js:1799)
at ui-router-angularjs.js:1849
at publicLinkFn (angular.js:9234)
at lazyCompilation (angular.js:9626)
at updateView (ui-router-angularjs.js:1838)
at Object.configUpdatedCallback [as configUpdated]
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: TeamCity Helper shows new failures in PRs

[Dmitrii Ryabov]

Hi, Dmitriy,

Webinar is good, but we need a page on the wiki (or "help" in the bot) for
new contributors. After that, I think we should add mention about helper to
the contributing guide.

2018-09-14 9:43 GMT+03:00 Nikolay Izhikov :

> Hello, Dmitriy.
>
> Webinar is a great idea, let's have it.
>
> В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> > Hi Folks,
> >
> > There is no description of this feature yet. But I think we should come
> > back to the idea of running a webinar.
> >
> > Please share your vision. If Igniters will attend I send an invitation to
> > the beginning of next week.
> >
> > I hope in the nearest time we will have a few more features to speak
> about.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov :
> >
> > > Hello, Dmitrii.
> > >
> > > Can you give a link to detailed description of this feature?
> > >
> > > Actually, I wonder if someone except bit developers know how to use it
> > >
> > > чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov :
> > >
> > > > Hello, Igniters!
> > > >
> > > > We've improved tests analysis in the TeamCity Helper.
> > > >
> > > > Now, when you view PR analysis, you can see a table with possible
> > >
> > > blockers
> > > > - failed tests and suites, that most likely appeared in the pull
> request.
> > > >
>

[jira] [Created] (IGNITE-9597) 'size() == 0' replaceable with 'isEmpty()' according inspections profile

[Maxim Muzafarov (JIRA)]

Maxim Muzafarov created IGNITE-9597:
---

 Summary: 'size() == 0' replaceable with 'isEmpty()' according 
inspections profile
 Key: IGNITE-9597
 URL: https://issues.apache.org/jira/browse/IGNITE-9597
 Project: Ignite
  Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov


New `Code Inspections` profile can be found 
{{\idea\ignite_inspections.xml}}.

We need to fix rule `size() == 0' replaceable with 'isEmpty()` in 
{{ignite-core}} module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: TeamCity Helper shows new failures in PRs

[Nikolay Izhikov]

Hello, Dmitriy.

Webinar is a great idea, let's have it.

В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> Hi Folks,
> 
> There is no description of this feature yet. But I think we should come
> back to the idea of running a webinar.
> 
> Please share your vision. If Igniters will attend I send an invitation to
> the beginning of next week.
> 
> I hope in the nearest time we will have a few more features to speak about.
> 
> Sincerely,
> Dmitriy Pavlov
> 
> чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov :
> 
> > Hello, Dmitrii.
> > 
> > Can you give a link to detailed description of this feature?
> > 
> > Actually, I wonder if someone except bit developers know how to use it
> > 
> > чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov :
> > 
> > > Hello, Igniters!
> > > 
> > > We've improved tests analysis in the TeamCity Helper.
> > > 
> > > Now, when you view PR analysis, you can see a table with possible
> > 
> > blockers
> > > - failed tests and suites, that most likely appeared in the pull request.
> > > 

signature.asc
Description: This is a digitally signed message part

Re: TeamCity Helper shows new failures in PRs

[Dmitriy Pavlov]

Hi Folks,

There is no description of this feature yet. But I think we should come
back to the idea of running a webinar.

Please share your vision. If Igniters will attend I send an invitation to
the beginning of next week.

I hope in the nearest time we will have a few more features to speak about.

Sincerely,
Dmitriy Pavlov

чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov :

> Hello, Dmitrii.
>
> Can you give a link to detailed description of this feature?
>
> Actually, I wonder if someone except bit developers know how to use it
>
> чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov :
>
> > Hello, Igniters!
> >
> > We've improved tests analysis in the TeamCity Helper.
> >
> > Now, when you view PR analysis, you can see a table with possible
> blockers
> > - failed tests and suites, that most likely appeared in the pull request.
> >
>