Re: checksum file Release Distribution Policy

On Tue, Mar 6, 2018 at 8:52 PM, Petr Ivanov wrote: > http://apache.org/dist/ignite/2.3.0/ > > Got it. Let's get rid of MD5 in this case. D.

[jira] [Created] (IGNITE-7902) Enable either swap space or persistence but not both

Prachi Garg created IGNITE-7902: --- Summary: Enable either swap space or persistence but not both Key: IGNITE-7902 URL: https://issues.apache.org/jira/browse/IGNITE-7902 Project: Ignite Issue

Re: [VOTE] Apache Ignite 2.4.0 RC1

+1, great work! 2018-03-07 19:34 GMT+03:00 Andrey Gura : > +1 > > Checked compilation under Java 8/9, examples, binaries checksums. > > On Wed, Mar 7, 2018 at 6:45 PM, Yury Babak wrote: > > +1 > > > > Checked Ignite ML: sources and binaries. > > > > Regards,

[jira] [Created] (IGNITE-7903) Explain how to tune performance by using WAL modes

Denis Magda created IGNITE-7903: --- Summary: Explain how to tune performance by using WAL modes Key: IGNITE-7903 URL: https://issues.apache.org/jira/browse/IGNITE-7903 Project: Ignite Issue

Re: MCTGA: .NET tests broken by IGNITE-6113

Hi Pavel, Thank you for pointing to this issue. We have detected it under Teamcity monitoring, but still any additional info on test failures is appreciated. I've checked PR run but did not noticed this failures, I have considered this failures as flaky: Ignite Platform .NET Core Linux [

MCTGA: .NET tests broken by IGNITE-6113

Igniters, Alexey G, Pavel K, IGNITE-6113 changes [1] caused broken .NET test [2] Have you run TeamCity before merging? Please fix this. When new APIs are added to Java you should: a) add them to .NET as well - or - b) file a ticket and update .NET test (see how in CacheParityTest.cs we have a

RE: Is ML a part of the Ignite.C# API? eom

Thanks Pavel. Will this target 2.5? -Original Message- From: Pavel Tupitsyn [mailto:ptupit...@apache.org] Sent: Wednesday, March 7, 2018 9:13 PM To: dev Cc: u...@ignite.apache.org Subject: Re: Is ML a part of the Ignite.C# API? eom Hi Raymond, This is planned,

Re: Is ML a part of the Ignite.C# API? eom

Hi Raymond, I guess it is not yet targetted to 2.5, because fix version is empty. Sincerely, Dmitriy Pavlov ср, 7 мар. 2018 г. в 11:54, Raymond Wilson : > Thanks Pavel. > > Will this target 2.5? > > -Original Message- > From: Pavel Tupitsyn

Re: DiscoverySpi based on Apache ZooKeeper

There is a section in the document https://apacheignite.readme.io/docs/cluster-config#zookeeper-based-discovery. but I found below two tickets. https://issues.apache.org/jira/browse/IGNITE-1203 https://issues.apache.org/jira/browse/IGNITE-7222 I am a bit confused about which version supports

[jira] [Created] (IGNITE-7897) Add example of using LSQR with data normalization

Anton Dmitriev created IGNITE-7897: -- Summary: Add example of using LSQR with data normalization Key: IGNITE-7897 URL: https://issues.apache.org/jira/browse/IGNITE-7897 Project: Ignite Issue

[GitHub] ignite pull request #3613: IGNITE-7773 Add 'rebalanceClearingPartitionsLeft'...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3613 IGNITE-7773 Add 'rebalanceClearingPartitionsLeft' metric to .NET You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

QueryEntity design

Hello, Igniters. I'm working on IGNITE-7691 [1] The goal of ticket is provide scale and precision info about DECIMAL columns. I see that QueryEntity has a separate collection for each type of meta information: * not null fields - [2] * default values - [3] Why we have such class design? It

[GitHub] ignite pull request #3599: IGNITE-5298 .NET: DML update via LINQ

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

[GitHub] ignite pull request #3595: IGNITE-7851: .NET: linq query throws Hexadecimal ...

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

Re: QueryEntity design

I do not think it is a big problem. We copy these values when starting node anyway, so subsequent changes doesn't affect node's behavior. On the other hand, this might be convenient to users in some cases. On Wed, Mar 7, 2018 at 3:13 PM, Nikolay Izhikov wrote: > Vladimir. >

Re: Thin client: transactions support

We already have transactions support in JDBC driver in TX SQL branch (ignite-4191). Currently it is implemented through separate thread, which is not that efficient. Ideally we need to finish decoupling transactions from threads. But alternatively we can change the logic on how we assign thread ID

[jira] [Created] (IGNITE-7901) Refactor Pages Write Throttling: introduce exponential throttle as separate class

Ivan Rakov created IGNITE-7901: -- Summary: Refactor Pages Write Throttling: introduce exponential throttle as separate class Key: IGNITE-7901 URL: https://issues.apache.org/jira/browse/IGNITE-7901

[GitHub] ignite pull request #3617: IGNITE-6860 Add logging and additional info while...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3617 IGNITE-6860 Add logging and additional info while BinaryMarshaller fa… …ils to serialize object. You can merge this pull request into a Git repository by running: $ git pull

Re: MCTGA: .NET tests broken by IGNITE-6113

Yep, this test is not flaky at all, it had failed before for the same exact reason, forgetting to update .NET. On Wed, Mar 7, 2018 at 12:13 PM, Dmitry Pavlov wrote: > Hi Pavel, > > Thank you for pointing to this issue. We have detected it under Teamcity > monitoring, but

[jira] [Created] (IGNITE-7899) Write Zookeeper Discovery documentation in java docs

Dmitry Sherstobitov created IGNITE-7899: --- Summary: Write Zookeeper Discovery documentation in java docs Key: IGNITE-7899 URL: https://issues.apache.org/jira/browse/IGNITE-7899 Project: Ignite

[GitHub] ignite pull request #3616: ignite-2.5.1.b2 - zooKeeper discovery fixes

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3616 ignite-2.5.1.b2 - zooKeeper discovery fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: QueryEntity design

Hi Nikolay, The answer is simple - legacy. QueryEntity was introduced long before we had rich SQL support. At this point we should consider both QueryEntity and our SQL API obsolete. There is a ticket to design new SQL API [1] and new "QueryEntity" should be it's integral part. If you have any

Re: QueryEntity design

Vladimir. Thank you, it's clear now. I also wonder, why we provide access to internal HashMaps through getters? Should we wrap internal maps into `Collections.unmodifiableMap`? ``` public Map getDefaultFieldValues() { return defaultFieldValues; } ``` В Ср,

Re: MCTGA: .NET tests broken by IGNITE-6113

Yes, it seems I need to do some update to https://github.com/dspavlov/ignite-teamcity-helper to reset fail rate after reasonable timeout/runs of tests. I quess 3 weeks and/or 100 successfull runs may be sufficient to consider test as fixed. WDYT? ср, 7 мар. 2018 г. в 15:02, Pavel Tupitsyn

[jira] [Created] (IGNITE-7900) Write Zookeeper Discovery documentation in readme.io

Dmitry Sherstobitov created IGNITE-7900: --- Summary: Write Zookeeper Discovery documentation in readme.io Key: IGNITE-7900 URL: https://issues.apache.org/jira/browse/IGNITE-7900 Project: Ignite

[jira] [Created] (IGNITE-7898) IgniteCachePartitionLossPolicySelfTest is flaky on TC

Pavel Kovalenko created IGNITE-7898: --- Summary: IgniteCachePartitionLossPolicySelfTest is flaky on TC Key: IGNITE-7898 URL: https://issues.apache.org/jira/browse/IGNITE-7898 Project: Ignite

[GitHub] ignite pull request #3614: IGNITE-7897 Add example for LSQR with data normal...

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

[GitHub] ignite pull request #3614: IGNITE-7897 Add example for LSQR with data normal...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3614 IGNITE-7897 Add example for LSQR with data normalization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3615: Ignite 2.3.1.b3

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3615 Ignite 2.3.1.b3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.3.1.b3 Alternatively you can review and

[GitHub] ignite pull request #3366: ignite-7396: fixed NullPointerException

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

Re: Is ML a part of the Ignite.C# API? eom

Hi, Dmitry I'm also looking forward to try ML on Ignite.NET platform, is there any idea when it is planned for release? On 7 March 2018 at 12:15, Dmitry Pavlov wrote: > Hi Raymond, > > I guess it is not yet targetted to 2.5, because fix version is empty. > > Sincerely, >

Re: [VOTE] Apache Ignite 2.4.0 RC1

+1 Checked Ignite ML: sources and binaries. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Is ML a part of the Ignite.C# API? eom

Hi Raymond, This is planned, but not yet implemented: https://issues.apache.org/jira/browse/IGNITE-6707 Pavel On Wed, Mar 7, 2018 at 5:56 AM, Raymond Wilson wrote: > … the reason I ask being that ML is included in the Ignite diagram in the > Ignite.C# documentation

[GitHub] ignite pull request #3598: IGNITE-7791: add additional logging

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

[GitHub] ignite pull request #3598: IGNITE-7791: add additional logging

GitHub user Mmuzaf reopened a pull request: https://github.com/apache/ignite/pull/3598 IGNITE-7791: add additional logging Logging for reproducing bug You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-7791

[GitHub] ignite pull request #3598: IGNITE-7791: add additional logging

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

[GitHub] ignite pull request #3618: IGNITE-7791: add test case for delayed partition ...

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3618 IGNITE-7791: add test case for delayed partition exchange …nect You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-7791

Re: DiscoverySpi based on Apache ZooKeeper

Hello Ken, Indeed tickets and documentation are confusing so let me clarify what they are about. Documentation at [1] and ticket IGNITE-1203 [2] are related to *TcpDiscoverySpi* component (see javadoc for in at [3]). More precisely they are about Zookeeper-based implementation of subcomponent

Re: [VOTE] Apache Ignite 2.4.0 RC1

+1 Checked compilation under Java 8/9, examples, binaries checksums. On Wed, Mar 7, 2018 at 6:45 PM, Yury Babak wrote: > +1 > > Checked Ignite ML: sources and binaries. > > Regards, > Yury > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/