Re: Apache Ignite RPM packaging (Stage II)

No, not yet. Currently we are discussing RPM packages only. I want to get all feedback and possible errors working on RPM packages, so that when we have stable agreed architecture and etc. I can recreate it in DEB packages without necessity to fix bugs in both RPM and DEB packages simultaneous

Re: Apache Ignite RPM packaging (Stage II)

Thanks, Petr! I would love to test the package installation, but I can only do it on Ubuntu. Do you know when will we be able to get the Debian instructions, similar to this: https://ignite.apache.org/download.cgi#rpm-package D. On Wed, Mar 28, 2018 at 12:01 AM, Petr Ivanov wrote: > No, not y

Re: Code inspection

Started https://ci.ignite.apache.org/viewLog.html?buildId=1164002 with Aleksey’s inspections profile. Core (long) and AOP (short) modules will be tested as example. > On 27 Mar 2018, at 19:38, Dmitry Pavlov wrote: > > Hi Petr, >

Ignite download page

Igniters, I think the Ignite Download page is getting too crowded. https://ignite.apache.org/download.cgi I would like to propose moving most of the previous versions to a separate page. For example, we can list 3 latest versions on the download page and older versions on another page. What do

Re: Ignite download page

+1 We can even make something like Maven download page [1]: point focus on latest version and add “Previous Releases” section, where all that tables with archived versions can be moved. [https://maven.apache.org/download.cgi ] > On 28 Mar 2018, at 10:3

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Pavel, At the moment it is only supported by thin clients. In future we will expand this mechanism to normal nodes as well. On Tue, Mar 27, 2018 at 10:55 AM, Pavel Tupitsyn wrote: > IGNITE-8034 done, I have added configuration flag. > > However, I still have concerns about property naming: > Is

[GitHub] ignite pull request #3711: failing zk tests turned off

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3711 failing zk tests turned off You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-zk-sch Alternatively yo

Re: Apache Ignite RPM packaging (Stage II)

I can start preparing DEB packages right after adding RPM build to nightly release build (as an experiment / experience for future addition of packages build into release process) basing on current RPM architecture. I will create branch from IGNITE-7647, then. > On 28 Mar 2018, at 10:06, Dmitr

Re: Ignite download page

+1 for the latest release and previous releases section. IMO, last three releases section doesn't make sense (Why three?). ср, 28 мар. 2018 г., 10:45 Petr Ivanov : > +1 > > We can even make something like Maven download page [1]: point focus on > latest version and add “Previous Releases” sectio

Re: MTCGA: Hot failures

Dmitriy, defenetely at first stage we need issues to be created. summary= TestN failed labels=MakeTeamCityGreenAgain text=Desctiption of failure. I hope Igniters could provide assitance in creation of issues related to these failures. Anton, as expert in Data Structures could you please check fa

Re: MTCGA: Hot failures

Dmitriy, Have no chances to check TC this week, may be later. 2018-03-28 13:16 GMT+03:00 Dmitry Pavlov : > Dmitriy, defenetely at first stage we need issues to be created. > summary= TestN failed > labels=MakeTeamCityGreenAgain > text=Desctiption of failure. > > I hope Igniters could provide ass

[GitHub] ignite pull request #3674: IGNITE-7682: CPP: Fixed constant for the LocalSiz...

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

[jira] [Created] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

Andrey Kuznetsov created IGNITE-8061: Summary: GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity Key: IGNITE-8061 URL: https://issues.apa

[jira] [Created] (IGNITE-8062) Add ability to properly wait for transaction finish in case of PRIMARY_SYNC cache mode

Pavel Kovalenko created IGNITE-8062: --- Summary: Add ability to properly wait for transaction finish in case of PRIMARY_SYNC cache mode Key: IGNITE-8062 URL: https://issues.apache.org/jira/browse/IGNITE-8062

[jira] [Created] (IGNITE-8063) Transaction rollback is unmanaged in case when commit produced Runtime exception

Pavel Kovalenko created IGNITE-8063: --- Summary: Transaction rollback is unmanaged in case when commit produced Runtime exception Key: IGNITE-8063 URL: https://issues.apache.org/jira/browse/IGNITE-8063

Apache Ignite nightly nuget upload

Hi, Pavel! While working on moving TC tests to new scheme, I stumbled across this build chain ([1] -> [2]). I wonder, after preparing nightly build project [3] - can I move task of nuget uploading to one of build step of that chain? IMO, nightly build in tests is a little bit out of place. [

[GitHub] ignite pull request #3712: IGNITE-6890: iep-14 implementation.

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3712 IGNITE-6890: iep-14 implementation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-6890-iep14 Alternatively you can

Re: Code inspection

After several problems, example run on Aleksey’s configuration is complete: https://ci.ignite.apache.org/viewLog.html?buildId=1164652 > On 28 Mar 2018, at 10:28, Petr Ivanov wrote: > > Started https://ci.ignite.apache.org/viewLog.htm

[jira] [Created] (IGNITE-8064) fix typos in JMX beans description

Max Shonichev created IGNITE-8064: - Summary: fix typos in JMX beans description Key: IGNITE-8064 URL: https://issues.apache.org/jira/browse/IGNITE-8064 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3713: IGNITE-8033 Flaky failure of TxOptimisticDeadlock...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3713 IGNITE-8033 Flaky failure of TxOptimisticDeadlockDetectionCrossCacheTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/

Re: Apache Ignite RPM packaging (Stage II)

> > We can either > store files as is (as Cassandra does, see link below) in something > that is called Generic Repository — this way we manage directory layouts > ourselves and have more control over what is published and how > or > store files in prepared RPM / DEB repositories wh

[jira] [Created] (IGNITE-8065) Some of PDS indexing tests became red after IGNITE-7902

Andrey Aleksandrov created IGNITE-8065: -- Summary: Some of PDS indexing tests became red after IGNITE-7902 Key: IGNITE-8065 URL: https://issues.apache.org/jira/browse/IGNITE-8065 Project: Ignite

Re: Code inspection

Peter, Why 44 errors are green? https://ci.ignite.apache.org/viewLog.html?buildId=1145974&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_InspectionsAop 2018-03-28 16:27 GMT+03:00 Petr Ivanov : > After several problems, example run on Aleksey’s configuration is > complete: https://ci.ignite.

[jira] [Created] (IGNITE-8066) Reset wal segment idx

Alexander Belyak created IGNITE-8066: Summary: Reset wal segment idx Key: IGNITE-8066 URL: https://issues.apache.org/jira/browse/IGNITE-8066 Project: Ignite Issue Type: New Feature

Re: Apache Ignite RPM packaging (Stage II)

Peter, great work! I'll check up PR in the near time. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Code inspection

Inspection suites should be failed manually by some fail condition. This question will become actual in future. How to fail such suite on TC? ср, 28 мар. 2018 г. в 18:54, Anton Vinogradov : > Peter, > > Why 44 errors are green? > > > https://ci.ignite.apache.org/viewLog.html?buildId=1145974&tab=

[jira] [Created] (IGNITE-8067) Java thin client code review: move parsing from TcpClientCache to ClientMessageParser

Alexey Kukushkin created IGNITE-8067: Summary: Java thin client code review: move parsing from TcpClientCache to ClientMessageParser Key: IGNITE-8067 URL: https://issues.apache.org/jira/browse/IGNITE-8067

[jira] [Created] (IGNITE-8068) Some tests failed due to JVM halt by default FailureHandler

Dmitriy Sorokin created IGNITE-8068: --- Summary: Some tests failed due to JVM halt by default FailureHandler Key: IGNITE-8068 URL: https://issues.apache.org/jira/browse/IGNITE-8068 Project: Ignite

[GitHub] ignite pull request #3714: IGNITE-8065 setSwapPath option used with enabled ...

GitHub user aealeksandrov opened a pull request: https://github.com/apache/ignite/pull/3714 IGNITE-8065 setSwapPath option used with enabled persistence was removed from some tests Some of PDS indexing tests became red after IGNITE-7902 The reason is that some tests enable

Near cache entry removal

Hi, Igniters! Currently, in atomic cache after we perform remove , GridNearCacheEntry still exists on 'reader' nodes. Why don't we remove it ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: Near cache entry removal

Hi, is this removal implemented for transactional cache? ср, 28 мар. 2018 г. в 19:49, Aleksey Kuznetsov : > Hi, Igniters! > > Currently, in atomic cache after we perform remove , > GridNearCacheEntry still exists on 'reader' nodes. > > Why don't we remove it ? > -- > > *Best Regards,* > > *Kuznet

Re: Near cache entry removal

Implemented for atomic cache > 28 марта 2018 г., в 20:24, Dmitry Pavlov написал(а): > > Hi, is this removal implemented for transactional cache? > > ср, 28 мар. 2018 г. в 19:49, Aleksey Kuznetsov : > >> Hi, Igniters! >> >> Currently, in atomic cache after we perform remove , >> GridNearCach

[GitHub] ignite pull request #3714: IGNITE-8065 setSwapPath option used with enabled ...

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

Re: Code inspection

Anton, Dmitry is right. We have to manually add condition when to consider build faulty based on how many failed inspection are there. For now I see this initiative as follows: - find more or less correct set of inspections (there are lots of typos and other irrelevant to code execution inspectio

[jira] [Created] (IGNITE-8069) IgniteOutOfMemoryException should be handled accordingly to provided failure handler

Andrey Gura created IGNITE-8069: --- Summary: IgniteOutOfMemoryException should be handled accordingly to provided failure handler Key: IGNITE-8069 URL: https://issues.apache.org/jira/browse/IGNITE-8069 Pr

[jira] [Created] (IGNITE-8070) .Net: FailureHandler should be added to Ignite configuration

Andrey Gura created IGNITE-8070: --- Summary: .Net: FailureHandler should be added to Ignite configuration Key: IGNITE-8070 URL: https://issues.apache.org/jira/browse/IGNITE-8070 Project: Ignite

[jira] [Created] (IGNITE-8071) Add tests for failure handlers

Andrey Gura created IGNITE-8071: --- Summary: Add tests for failure handlers Key: IGNITE-8071 URL: https://issues.apache.org/jira/browse/IGNITE-8071 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-8072) SQL query with multiple JOIN and subquery with UNION produces "Column not found" exception

Pavel Vinokurov created IGNITE-8072: --- Summary: SQL query with multiple JOIN and subquery with UNION produces "Column not found" exception Key: IGNITE-8072 URL: https://issues.apache.org/jira/browse/IGNITE-8072