Re: Ticket review checklist

Dmitry, I still do not see how new patches could be accepted with this requirement in place. Consider the following case: I created a patch and run it on TC, observed N failures, verified through TC history that none if them are new. Am I eligible to push the commit? On Thu, May 24, 2018 at 3:11

[jira] [Created] (IGNITE-8685) Incorrect size for switch segment record

Dmitriy Govorukhin created IGNITE-8685: -- Summary: Incorrect size for switch segment record Key: IGNITE-8685 URL: https://issues.apache.org/jira/browse/IGNITE-8685 Project: Ignite Issue

[jira] [Created] (IGNITE-8686) Web console: 'Get started' point to the wrong page

Pavel Konstantinov created IGNITE-8686: -- Summary: Web console: 'Get started' point to the wrong page Key: IGNITE-8686 URL: https://issues.apache.org/jira/browse/IGNITE-8686 Project: Ignite

[jira] [Created] (IGNITE-8688) Pending tree is initialized outside of checkpoint lock

Pavel Kovalenko created IGNITE-8688: --- Summary: Pending tree is initialized outside of checkpoint lock Key: IGNITE-8688 URL: https://issues.apache.org/jira/browse/IGNITE-8688 Project: Ignite

Re: Ticket review checklist

Hi Vladimir, could you provide definition what is new failure? how do you know it is new or not? And please forget for a moment you're Ignite expert & veteran, imagine you are newcomer. I can't find any criteria that can be used by newbie to come to the conclusion that test is new. Patch is

Re: Ticket review checklist

Dmitry, New failure is a failure hasn't happened on previous runs. If it do happened, then contributor should see if it is a flaky or not through local and TC runs. The same works for timeout suites. Current statement in "Review Checklist" that there are should be no failed tests is not

[jira] [Created] (IGNITE-8690) Missed package-info for some packages

Pavel Kovalenko created IGNITE-8690: --- Summary: Missed package-info for some packages Key: IGNITE-8690 URL: https://issues.apache.org/jira/browse/IGNITE-8690 Project: Ignite Issue Type: Bug

Re: Ticket review checklist

Vladimir, I mean strict definition, how much previous runs should contributor consider? What if test was failed by infrastructure reason in master previously, how can contributor be sure test failure != broken code in PR? In this case it should be double checked by contributor/reviewer. I'm sure

Re: Ticket review checklist

Dmitry, My question was how to proceed with your rules. Could you please clarify? On Mon, Jun 4, 2018 at 2:52 PM, Dmitry Pavlov wrote: > Vladimir, I mean strict definition, how much previous runs should > contributor consider? What if test was failed by infrastructure reason in > master

[jira] [Created] (IGNITE-8693) SQL JOIN between PARTITIONED and REPLICATED cache fails

Ilya Lantukh created IGNITE-8693: Summary: SQL JOIN between PARTITIONED and REPLICATED cache fails Key: IGNITE-8693 URL: https://issues.apache.org/jira/browse/IGNITE-8693 Project: Ignite

Re: Ticket review checklist

Requirement of green TC for each PR is community rule, not my. I'll answer ro another question, what should we do with test failure: "Ideally - fix, but at least mute test and create ticket. " May be it's time to formalize Make TC Green Again process in details, so let me share my draft. If

[GitHub] ignite pull request #4116: IGNITE-8690 Added missed package-infos.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4116 ---

[jira] [Created] (IGNITE-8691) Get rid of tests jar artifact in ignite-zookeeper module

Pavel Kovalenko created IGNITE-8691: --- Summary: Get rid of tests jar artifact in ignite-zookeeper module Key: IGNITE-8691 URL: https://issues.apache.org/jira/browse/IGNITE-8691 Project: Ignite

[GitHub] ignite pull request #4105: IGNITE-8675: Fixed flacky test PdsWithTtlCompatib...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4105 ---

[GitHub] ignite pull request #4116: IGNITE-8690 Added missed package-infos.

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4116 IGNITE-8690 Added missed package-infos. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8690 Alternatively you

[jira] [Created] (IGNITE-8692) MVCC TX: Always persistent TxLog

Igor Seliverstov created IGNITE-8692: Summary: MVCC TX: Always persistent TxLog Key: IGNITE-8692 URL: https://issues.apache.org/jira/browse/IGNITE-8692 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #4120: IGNITE-8693 : Fix for SQL JOIN between REPLICATED...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/4120 IGNITE-8693 : Fix for SQL JOIN between REPLICATED and PARTITIONED caches …hes. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8689) SQL query execution may lead to NullPointerException during node stop.

Vyacheslav Koptilin created IGNITE-8689: --- Summary: SQL query execution may lead to NullPointerException during node stop. Key: IGNITE-8689 URL: https://issues.apache.org/jira/browse/IGNITE-8689

[GitHub] ignite pull request #4115: IGNITE-8290: Trying to reproduce on TC.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4115 IGNITE-8290: Trying to reproduce on TC. Debug through CI. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Dmitriy, I’ve added requested information (see [1]). Can you check that this information is enough, please? [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCommentId=16500123=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16500123 > On 3 Jun 2018, at

[GitHub] ignite pull request #4118: IGNITE-8691 Removed jar-plugin from ignite-zookee...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4118 IGNITE-8691 Removed jar-plugin from ignite-zookeeper module You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8691

[GitHub] ignite pull request #4117: IGNITE-8663: Add Normalization Preprocessing supp...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4117 IGNITE-8663: Add Normalization Preprocessing support You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8663

Re: Upgrading Ignite to JCache 1.1

Hi, Igniters! I have taken a look at the jcache 1.1 spec and TCK. And I can write a brief summary of my plan to solve the task. I have found 6 problems in current master with TCK 1.1 (104 failed tests). Of course, we should run this TCK on CI to be absolutely sure we didn't miss something. So

[GitHub] ignite pull request #4119: Ignite 5954 30 time run test

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/4119 Ignite 5954 30 time run test You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-5954-30-time-run-test Alternatively you can

[GitHub] ignite pull request #4121: IGNITE-8562: Squashed partial commits.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4121 IGNITE-8562: Squashed partial commits. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-8562

[GitHub] ignite pull request #4118: IGNITE-8691 Removed jar-plugin from ignite-zookee...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4118 ---

Re: What's new for thin client protocol v1.1.0 vs v1.0.0

Hi Aleksandr, There are no changes other than username/password support. But that's a good point to start a discussion on how do we publish Thin Protocol changes. I'll start a thread for it on devlist - feel free to take part in it. Best Regards, Igor On Sun, Jun 3, 2018 at 11:23 AM, Aleksandr

Re: What's new for thin client protocol v1.1.0 vs v1.0.0

Hello, Igniters. AFAIK, we have backward compatibility for a thin client protocol. But, currently, we doesn't have any kind of tests to check it. Do we have a ticket to create backward compatibility tests? В Пн, 04/06/2018 в 13:30 +0300, Igor Sapego пишет: > Hi Aleksandr, > > There are no

[jira] [Created] (IGNITE-8687) Add JCache TCK 1.1.0 to TC

Alexander Menshikov created IGNITE-8687: --- Summary: Add JCache TCK 1.1.0 to TC Key: IGNITE-8687 URL: https://issues.apache.org/jira/browse/IGNITE-8687 Project: Ignite Issue Type:

Re: What's new for thin client protocol v1.1.0 vs v1.0.0

No, we don't AFAIK. Feel free to create one. Best Regards, Igor On Mon, Jun 4, 2018 at 1:34 PM, Nikolay Izhikov wrote: > Hello, Igniters. > > AFAIK, we have backward compatibility for a thin client protocol. > But, currently, we doesn't have any kind of tests to check it. > > Do we have a

Thin client protocol version release notes.

Igniters, Currently, our thin client specification is kept on readme.io [1]. However, sometimes to introduce new features while keeping backward compatibility, we need to increase protocol version. The issue is: there is currently no easy way for thin client developers to find out when thin

[GitHub] ignite pull request #4114: ignite-8687 Add JCache TCK 1.1.0 to TC

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/4114 ignite-8687 Add JCache TCK 1.1.0 to TC For [IGNITE-8687](https://issues.apache.org/jira/browse/IGNITE-8687) You can merge this pull request into a Git repository by running: $ git pull

Re: Thin client protocol version release notes.

The change list page is a good offer. As for the versions, it's clear that the protocol version differs from an Ignite one. However, a next protocol version officially becomes available with a next Ignite release meaning. For me, it means, all the new protocol changes need to be documented on a

Re: Apache Ignite 2.6 - Packages roadmap

Petr, I do remember the multi-package approach was suggested as a solution to trim down the size of the binary that is hosted by ASF. Since now the binaries are hosted in Bintray, do we still have that issue? If it's fine to preload and keep big binaries in Bintray then I would suggest us to

Re: Apache Ignite 2.6 - Packages roadmap

Here is my list: 1. Remove the requirement to run Ignite scripts as root. This will be a huge No in most environment and we should fix it. 2. Add Ignite "bin" folder to PATH, so all Ignite scripts will be executable without specifying the whole path name (not sure if it is already

Re: Apache Ignite 2.6 - Packages roadmap

There is already a ticket for point 1: https://issues.apache.org/jira/browse/IGNITE-8695 -- Denis On Mon, Jun 4, 2018 at 2:40 PM, Dmitriy Setrakyan wrote: > Here is my list: > >1. Remove the requirement to run Ignite scripts as root. This will be a >huge No in most environment and we

[jira] [Created] (IGNITE-8695) RPM|DEB: Remove requirement to run Ignite stand-along under root

Denis Magda created IGNITE-8695: --- Summary: RPM|DEB: Remove requirement to run Ignite stand-along under root Key: IGNITE-8695 URL: https://issues.apache.org/jira/browse/IGNITE-8695 Project: Ignite

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Dmitriy, thanks! Fixed that typo. > On 4 Jun 2018, at 17:09, Dmitriy Setrakyan wrote: > > Peter, can you please fix the text below to point to "log", not "lib"? > > log directory is at /var/lib/apache-ignite (mapped to >> /var/lib/apache-ignite/log) > > > On Mon, Jun 4, 2018 at 7:07 AM,

Apache Ignite 2.6 - Packages roadmap

Igniters! Apache Ignite 2.5 is released and for the first time in it’s history is shipped in both RPM and DEB packages. And, I think, it is time to discuss the future roadmap of Apache Ignite in Linux packages initiative. For the first “feature” I would suggest splitting of the packages on

[GitHub] ignite pull request #4124: IGNITE-8667 Splitting of dataset to test and trai...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/4124 IGNITE-8667 Splitting of dataset to test and training sets You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4120: IGNITE-8693 : Fix for SQL JOIN between REPLICATED...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4120 ---

[jira] [Created] (IGNITE-8698) Presto can't query tables in ignite with '_' in name.

arklet created IGNITE-8698: -- Summary: Presto can't query tables in ignite with '_' in name. Key: IGNITE-8698 URL: https://issues.apache.org/jira/browse/IGNITE-8698 Project: Ignite Issue Type: Bug

Re: Apache Ignite 2.6 - Packages roadmap

> 1. Remove the requirement to run Ignite scripts as root. This will be a > huge No in most environment and we should fix it. > There is already a ticket for point 1: > https://issues.apache.org/jira/browse/IGNITE-8695 > 1. I am not the

Re: Apache Ignite 2.6 - Packages roadmap

Petr, I think it was Denis who reworked the documentation. In any case, if you see something lacking you can fix it. Just to clarify, are you suggesting that you don't have to be root to run the Ignite process after the package install? D. On Mon, Jun 4, 2018 at 9:31 PM, Petr Ivanov wrote: >

Re: Upgrading Ignite to JCache 1.1

Thanks, Alex! Sounds like a good plan. On Mon, Jun 4, 2018 at 5:52 AM, Александр Меньшиков wrote: > Hi, > Igniters! > > I have taken a look at the jcache 1.1 spec and TCK. > And I can write a brief summary of my plan to solve the task. > > I have found 6 problems in current master with TCK 1.1

[jira] [Created] (IGNITE-8697) Flink sink throws java.lang.IllegalArgumentException when running in flink cluster mode.

Ray created IGNITE-8697: --- Summary: Flink sink throws java.lang.IllegalArgumentException when running in flink cluster mode. Key: IGNITE-8697 URL: https://issues.apache.org/jira/browse/IGNITE-8697 Project:

[jira] [Created] (IGNITE-8696) control.sh utility does not show atomicity mode

Sergey Kosarev created IGNITE-8696: -- Summary: control.sh utility does not show atomicity mode Key: IGNITE-8696 URL: https://issues.apache.org/jira/browse/IGNITE-8696 Project: Ignite Issue

[GitHub] ignite pull request #4127: IGNITE-8696 add cache atomicity to cache list inf...

GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/4127 IGNITE-8696 add cache atomicity to cache list info You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8696

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Log directory is directly at /var/log/apache-ignite and mapped via symlink to /var/lib/apache-ignite/log because /var/lib/apache-ignite/ (main work dir which in its turn is mapped via symlink to /usr/share/apache—ignite/work) is the place where running node of Apache Ignite will write it’s

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Peter, can you please fix the text below to point to "log", not "lib"? log directory is at /var/lib/apache-ignite (mapped to > /var/lib/apache-ignite/log) On Mon, Jun 4, 2018 at 7:07 AM, Petr Ivanov wrote: > Log directory is directly at /var/log/apache-ignite and mapped via symlink > to

[GitHub] ignite pull request #4122: GG-13862

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/4122 GG-13862 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13862 Alternatively you can review and apply these

[GitHub] ignite pull request #4123: 1.9.13 stale

GitHub user antkr opened a pull request: https://github.com/apache/ignite/pull/4123 1.9.13 stale CI partial tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite 1.9.13-stale Alternatively you can review

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Thanks, Petr! I think the log directory should be at /var/log, not /var/lib, right? D. On Mon, Jun 4, 2018 at 5:04 AM, Petr Ivanov wrote: > Dmitriy, > > > I’ve added requested information (see [1]). > Can you check that this information is enough, please? > > > [1]

Re: Thin client protocol version release notes.

Hi Igor, That's a great idea! This would make the client developers' lives much easier. Pavel On Mon, Jun 4, 2018 at 3:54 AM, Igor Sapego wrote: > Igniters, > > Currently, our thin client specification is kept on readme.io [1]. > However, sometimes to introduce new features while keeping >

[jira] [Created] (IGNITE-8694) SQL JOIN between PARTITIONED and REPLICATED cache fails

Ivan Rakov created IGNITE-8694: -- Summary: SQL JOIN between PARTITIONED and REPLICATED cache fails Key: IGNITE-8694 URL: https://issues.apache.org/jira/browse/IGNITE-8694 Project: Ignite Issue

[GitHub] ignite pull request #4123: 1.9.13 stale

Github user antkr closed the pull request at: https://github.com/apache/ignite/pull/4123 ---

[GitHub] ignite pull request #4125: IGNITE-8694 SQL JOIN between PARTITIONED and REPL...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4125 IGNITE-8694 SQL JOIN between PARTITIONED and REPLICATED cache fails Signed-off-by: Ivan Rakov You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #4126: reproducer for atomic cache inconsistent state

GitHub user dgarus opened a pull request: https://github.com/apache/ignite/pull/4126 reproducer for atomic cache inconsistent state You can merge this pull request into a Git repository by running: $ git pull https://github.com/dgarus/ignite inc_atomic Alternatively you can

Re: Apache Ignite 2.6 - Packages roadmap

Hello! Here's my list of improvements for AI package: - Make sqlline.sh callable from command line (PATH). E.g. symlink it as /usr/bin/sqlline-ignite, make sure it works. - Fix control.sh and visor-cmd, expose them too. - Allow specifying of JDK implementation and JDK arguments for Apache Ignite