[jira] [Created] (IGNITE-6072) SQL: client node should not hold the whole data set in-memory when possible when merge table is there

Vladimir Ozerov created IGNITE-6072: --- Summary: SQL: client node should not hold the whole data set in-memory when possible when merge table is there Key: IGNITE-6072 URL:

Re: Resurrect FairAffinityFunction

Vladimir, I think you should look more carefully at what FairAffinity does and why it exists. There is no way to "fix" it not to accept previous state - it must be provided. I do not understand why we need to change anything in code when there is a simple solution being proposed here. Why not

Re: Resurrect FairAffinityFunction

On Tue, Aug 15, 2017 at 10:35 PM, Vladimir Ozerov wrote: > Valya, > > And this is the problem! ) We have another implementation which minimizes > movements - rendezvous. Fair affinity should not bother about partition > migration. This is not a feature, but a bug in

Re: Ignite not friendly for Monitoring

Denis, IGNITE-5620 is completely different thing. Let's do not mix cluster monitoring and parser errors. ср, 16 авг. 2017 г. в 2:57, Denis Magda : > Alexey, > > Didn’t know that such an improvement as consistent IDs for errors and > events can be used as an integration point

[GitHub] ignite pull request #2430: IGNITE-6019

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2430 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-6073) Handy APIs to add binary metadata locally and to iterate over registered binary types

Sergey Chugunov created IGNITE-6073: --- Summary: Handy APIs to add binary metadata locally and to iterate over registered binary types Key: IGNITE-6073 URL: https://issues.apache.org/jira/browse/IGNITE-6073

Policy for update third-party dependencies

Hi, All! Do we have any policy for updating third-party dependencies? For example, I found that we are using very old Apache Common codec v.1.6 (released in 2011) And latest is Apache Common codec v.1.10 Do we need to update to new versions from time to time? And how? Just create JIRA issue,

[GitHub] ignite pull request #2450: IGNITE-5145 add batch service deployment methods

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/2450 IGNITE-5145 add batch service deployment methods You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5145

[jira] [Created] (IGNITE-6074) Test fail IgniteWalRecoveryTest#testWalBigObjectNodeCancel

Dmitriy Govorukhin created IGNITE-6074: -- Summary: Test fail IgniteWalRecoveryTest#testWalBigObjectNodeCancel Key: IGNITE-6074 URL: https://issues.apache.org/jira/browse/IGNITE-6074 Project:

Re: Resurrect FairAffinityFunction

I already explained why checking specifically for FairAffintiyFunction in SQL is wrong. On Wed, Aug 16, 2017 at 10:00 AM, Dmitriy Setrakyan wrote: > Vladimir, I think you should look more carefully at what FairAffinity does > and why it exists. There is no way to "fix" it

Re: Resurrect FairAffinityFunction

I am still not quite understand why we bother so much about partition migration while we already have RendezvousAffinityFunction? Looks like we tried to make "fair" be closer to "rendezvous", and then tried to make "rendezvous" closer to "fair", but without any success: - we are still not

[GitHub] ignite pull request #2419: IGNITE-5452 GridTimeoutProcessor can hang on stop

Github user dmekhanikov closed the pull request at: https://github.com/apache/ignite/pull/2419 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #2452: IGNITE-6074 fix test fail testWalBigObjectNodeCan...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2452 IGNITE-6074 fix test fail testWalBigObjectNodeCancel reset position and limit after expand buffer You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6078) Possible deadlock on concurrent grid stop

Igor Seliverstov created IGNITE-6078: Summary: Possible deadlock on concurrent grid stop Key: IGNITE-6078 URL: https://issues.apache.org/jira/browse/IGNITE-6078 Project: Ignite Issue

[jira] [Created] (IGNITE-6079) SQL: implement base table statistics

Vladimir Ozerov created IGNITE-6079: --- Summary: SQL: implement base table statistics Key: IGNITE-6079 URL: https://issues.apache.org/jira/browse/IGNITE-6079 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6080) SQL: Batch DML updates on per-node basis

Vladimir Ozerov created IGNITE-6080: --- Summary: SQL: Batch DML updates on per-node basis Key: IGNITE-6080 URL: https://issues.apache.org/jira/browse/IGNITE-6080 Project: Ignite Issue Type:

[GitHub] ignite pull request #2451: Fixed races related to partition eviction and re-...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2451 Fixed races related to partition eviction and re-creation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-6075) CacheLoadingConcurrentGridStartSelfTest sometimes fails

Igor Seliverstov created IGNITE-6075: Summary: CacheLoadingConcurrentGridStartSelfTest sometimes fails Key: IGNITE-6075 URL: https://issues.apache.org/jira/browse/IGNITE-6075 Project: Ignite

[jira] [Created] (IGNITE-6076) SQL: Local query should not go through map-reduce phase

Vladimir Ozerov created IGNITE-6076: --- Summary: SQL: Local query should not go through map-reduce phase Key: IGNITE-6076 URL: https://issues.apache.org/jira/browse/IGNITE-6076 Project: Ignite

[GitHub] ignite pull request #2452: IGNITE-6074 fix test fail testWalBigObjectNodeCan...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2452 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-6077) IgniteWalRecoveryTest.testWalRolloverMultithreadedDefault fails

Sergey Chugunov created IGNITE-6077: --- Summary: IgniteWalRecoveryTest.testWalRolloverMultithreadedDefault fails Key: IGNITE-6077 URL: https://issues.apache.org/jira/browse/IGNITE-6077 Project:

[GitHub] ignite pull request #2453: Ignite 1.8.9 p2

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

[GitHub] ignite pull request #2358: IGNITE-GG-12549-1.9.5 SQL: Add support for Java 8...

Github user asfedotov closed the pull request at: https://github.com/apache/ignite/pull/2358 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Batch service deployment

I've had a few off-line conversations with other Igniters regarding this question and almost all of them think that services should be deployed with "all-or-none" failing policy. We have a similar functionality for caches: Ignite#createCaches method don't allow partial deployments, and I think, we

[GitHub] ignite pull request #2458: IGNITE-GG-12549-1.9.6

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/2458 IGNITE-GG-12549-1.9.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12549 Alternatively you can review

[jira] [Created] (IGNITE-6081) .NET: Cannot get from cache values which were stored in cache with PutAll.

Igor Sapego created IGNITE-6081: --- Summary: .NET: Cannot get from cache values which were stored in cache with PutAll. Key: IGNITE-6081 URL: https://issues.apache.org/jira/browse/IGNITE-6081 Project:

[GitHub] ignite pull request #2454: IGNITE-6080

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2454 IGNITE-6080 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6080 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6082) Test fail DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentPutRemove

Dmitriy Govorukhin created IGNITE-6082: -- Summary: Test fail DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentPutRemove Key: IGNITE-6082 URL:

[jira] [Created] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing

Vladislav Pyatkov created IGNITE-6083: - Summary: Null value have appear in the entry processor, but the entry is existing Key: IGNITE-6083 URL: https://issues.apache.org/jira/browse/IGNITE-6083

[jira] [Created] (IGNITE-6087) SQL: Ability to pass one column to multiple object fields

Vladimir Ozerov created IGNITE-6087: --- Summary: SQL: Ability to pass one column to multiple object fields Key: IGNITE-6087 URL: https://issues.apache.org/jira/browse/IGNITE-6087 Project: Ignite

Re: Policy for update third-party dependencies

The answer is Yes, we should update. Jira ticket assigned to the next release should be enough in my view. D. On Wed, Aug 16, 2017 at 2:38 AM, Alexey Kuznetsov wrote: > Hi, All! > > Do we have any policy for updating third-party dependencies? > > For example, I found

Re: Multi-Version Concurrency Control

Hi Alex, Thanks a lot for your feedback! #1 Could you please share any case when we need to use different modes for different caches? It's a quite global thing to support two modes on the same time. #2 Certain we can use another name. "Extinct Version Ejection" for example. BR, Serge On Tue,

[jira] [Created] (IGNITE-6084) SQL: improve lazy execution threading model

Vladimir Ozerov created IGNITE-6084: --- Summary: SQL: improve lazy execution threading model Key: IGNITE-6084 URL: https://issues.apache.org/jira/browse/IGNITE-6084 Project: Ignite Issue

[jira] [Created] (IGNITE-6085) SQL: JOIN with multiple conditions is extremely slow

Vladimir Ozerov created IGNITE-6085: --- Summary: SQL: JOIN with multiple conditions is extremely slow Key: IGNITE-6085 URL: https://issues.apache.org/jira/browse/IGNITE-6085 Project: Ignite

[jira] [Created] (IGNITE-6086) SQL: create own parser for DDL and control statements

Vladimir Ozerov created IGNITE-6086: --- Summary: SQL: create own parser for DDL and control statements Key: IGNITE-6086 URL: https://issues.apache.org/jira/browse/IGNITE-6086 Project: Ignite

[GitHub] ignite pull request #2455: IGNITE-5879 .NET: Move TestPlatformPlugin to a se...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2455 IGNITE-5879 .NET: Move TestPlatformPlugin to a separate module You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5879

[GitHub] ignite pull request #2456: Add test for https://issues.apache.org/jira/brows...

GitHub user red-batmen opened a pull request: https://github.com/apache/ignite/pull/2456 Add test for https://issues.apache.org/jira/browse/IGNITE-3935 Writing test for IGNITE-3935 You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2456: Add test for https://issues.apache.org/jira/brows...

Github user red-batmen closed the pull request at: https://github.com/apache/ignite/pull/2456 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Created] (IGNITE-6088) Socket#shutdownOutput in ServerImpl lead UnsupportedOperationException on SSLSocket

Evgenii Zhuravlev created IGNITE-6088: - Summary: Socket#shutdownOutput in ServerImpl lead UnsupportedOperationException on SSLSocket Key: IGNITE-6088 URL: https://issues.apache.org/jira/browse/IGNITE-6088

[jira] [Created] (IGNITE-6089) SQL: Improve query parallelism architecture

Vladimir Ozerov created IGNITE-6089: --- Summary: SQL: Improve query parallelism architecture Key: IGNITE-6089 URL: https://issues.apache.org/jira/browse/IGNITE-6089 Project: Ignite Issue

[GitHub] ignite pull request #2457: IGNITE-6088 Socket#shutdownOutput in ServerImpl l...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2457 IGNITE-6088 Socket#shutdownOutput in ServerImpl leads to UnsupportedO… …perationException on SSLSocket You can merge this pull request into a Git repository by running: $ git pull

Re: Service versioning

Ilya, I think the proposed change definitely makes sense. At the same time I think the scope of the ticket is too broad. It covers at least two different aspects of service grid functionality: - Very specific issue of service upgrade process which is caused by current design flaw

[GitHub] ignite pull request #2459: ignite-5497

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/2459 ignite-5497 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.4-b1 Alternatively you can review and apply

Re: Multi-Version Concurrency Control

Serge, >#1 Could you please share any case when we need to use different modes for >different caches? Atomic caches? -- Alexey Kuznetsov

[GitHub] ignite pull request #2460: IGNITE-5790 SQL: Append UUID to names of Ignite i...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2460 IGNITE-5790 SQL: Append UUID to names of Ignite instances opened by JDBC All Ignite instances created by Jdbc driver should now be either named or appended with ignite-jdbc-driver-UUID to avoid

Re: [Webinar] Apache Process Overview, Aug 10, 2017 9.00 AM - 10.00 AM PT

Thanks for posting the recording, guys! Here are the slides to go with it [1] [1] https://mega.nz/#!Bp0xAYYC!IntSc8idFUKRgw0Nr04q1HJWGHTw5mxS3pp5nKlI4_M -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email

Re: Redesigning Ignite's site Look & Feel

Looks very cool! My first comment is that the home page looks different in Windows Edge from Mac. For example, the font of the "Memory-Centric Data Platform" is different and bold is not visible in Windows. D. On Wed, Aug 16, 2017 at 4:30 PM, Denis Magda wrote: > Igniters,

Re: Batch service deployment

On Wed, Aug 16, 2017 at 8:17 AM, Denis Mekhanikov wrote: > I've had a few off-line conversations with other Igniters regarding this > question and almost all of them think that services should be deployed with > "all-or-none" failing policy. > We have a similar

Re: SQL usability issues

Denis, I agree with Val. I am OK with using DBeaver as an example, but the name of the doc should be generic and the doc should be updated stating that DBeaver is just one example of how Ignite can be used with generic SQL viewer tools. D. On Wed, Aug 16, 2017 at 6:01 PM, Denis Magda

Re: Redesigning Ignite's site Look & Feel

I cannot open this url. It is working? On Thu, Aug 17, 2017 at 8:16 AM, Dmitriy Setrakyan wrote: > Looks very cool! > > My first comment is that the home page looks different in Windows Edge from > Mac. For example, the font of the "Memory-Centric Data Platform" is >

Re: SQL usability issues

Val, This article is generic: https://apacheignite.readme.io/docs/getting-started-sql DBeaver, Pentaho and Tableau are given as examples. If the description or introduction of the tool should sound clearer please suggest your version.

Re: Policy for update third-party dependencies

Denis, > I would respond why do we need to update? Some bug, new capabilities, > security breach? Alexey K., please shed some light on this. There is no special purpose, I just accidentally found that we are using very old dependency. It is common practice (especially in web development (as

Re: Ignite2.1: Page eviction is not compatible with persistence when startup

On Wed, Aug 16, 2017 at 3:39 PM, Denis Magda wrote: > Developers, > > Let me bring this to your attention. Why do we throw an exception if the > user has both an eviction policy and the Ignite persistence configured? Why > don’t we simply ignore the eviction policy printing a

Re: SQL usability issues

Denis, I think this article should be more generic, describing how to connect a generic JDBC tool to Ignite (probably using DBeaver as an example). Right now it looks like out of all such tools we support only DBeaver for some reason :) What do you think? -Val On Wed, Aug 16, 2017 at 1:49 PM,

Ignite Add-on/Extension Request: Please add GA Grid (beta) to Ignite website

Forum Admin, Please add project: GA Grid (beta): Distributive in Memory Genetic Algorithm component for Ignite to "Addons and Extensions" section of Apache Ignite website: https://ignite.apache.org/addons.html

Re: Policy for update third-party dependencies

Done https://issues.apache.org/jira/browse/IGNITE-6090 On Wed, Aug 16, 2017 at 8:01 PM, Dmitriy Setrakyan wrote: > The answer is Yes, we should update. Jira ticket assigned to the next > release should be enough in my view. > > D. > > On Wed, Aug 16, 2017 at 2:38 AM,

[jira] [Created] (IGNITE-6090) Update Apache Common codec from 1.6 to 1.10

Alexey Kuznetsov created IGNITE-6090: Summary: Update Apache Common codec from 1.6 to 1.10 Key: IGNITE-6090 URL: https://issues.apache.org/jira/browse/IGNITE-6090 Project: Ignite Issue

[GitHub] ignite pull request #2461: gg-12637 Fixed unevenly partitions distribution i...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/2461 gg-12637 Fixed unevenly partitions distribution in FairAffinityFunction You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite

Re: SQL Getting Started Guide

Igniters, The SQL getting started guide is ready and published: https://apacheignite.readme.io/v2.1/docs/getting-started-sql Akmal thanks for your efforts and please apply the following minor changes: * Add ODBC source files to your

Re: SQL usability issues

Igniters, I’ve prepared the getting started basing on DBeaver tool: https://apacheignite-tools.readme.io/docs/dbeaver That guide is based on the generic one made out by Akmal: https://apacheignite.readme.io/docs/getting-started-sql

Re: Policy for update third-party dependencies

I would respond why do we need to update? Some bug, new capabilities, security breach? Alexey K., please shed some light on this. — Denis > On Aug 16, 2017, at 5:12 PM, Dmitriy Setrakyan wrote: > > On Wed, Aug 16, 2017 at 5:02 PM, Denis Magda wrote:

Fwd: .sha Release Distribution Policy

Igniters, especially the release managers, Please consider these changes and recommendations for the next release. Do we have any ticket that already takes this into account? — Denis > Begin forwarded message: > > From: "Henk P. Penning" > Subject: .sha Release Distribution

Re: Policy for update third-party dependencies

On Wed, Aug 16, 2017 at 5:26 PM, Denis Magda wrote: > I would respond why do we need to update? Some bug, new capabilities, > security breach? Alexey K., please shed some light on this. > Actually, now that I think of it, why do we even have that dependency? But if you do,

Fwd: Ignite2.1: Page eviction is not compatible with persistence when startup

Developers, Let me bring this to your attention. Why do we throw an exception if the user has both an eviction policy and the Ignite persistence configured? Why don’t we simply ignore the eviction policy printing a warning and proceed with the node startup? — Denis > Begin forwarded message:

[jira] [Created] (IGNITE-6092) Bulk Inserts are not Supported

Denis Magda created IGNITE-6092: --- Summary: Bulk Inserts are not Supported Key: IGNITE-6092 URL: https://issues.apache.org/jira/browse/IGNITE-6092 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-6091) Test fail CacheLateAffinityAssignmentTest.testRandomOperations

Dmitriy Govorukhin created IGNITE-6091: -- Summary: Test fail CacheLateAffinityAssignmentTest.testRandomOperations Key: IGNITE-6091 URL: https://issues.apache.org/jira/browse/IGNITE-6091 Project:

Redesigning Ignite's site Look & Feel

Igniters, Some of us have been working on the new design for the site. That’s an early draft we have. Feel free to share the suggestions: http://81.156.86.10:8081/index.html In the meanwhile, is it possible to request a staging environment for the site

Re: Policy for update third-party dependencies

Honestly, I wouldn’t touch a dependency if it works like a charm and nobody requested us to migrate to a new version. Why do you need to update Apache Common coded? — Denis > On Aug 16, 2017, at 10:36 AM, Alexey Kuznetsov wrote: > > Done > >

Re: Policy for update third-party dependencies

On Wed, Aug 16, 2017 at 5:02 PM, Denis Magda wrote: > Honestly, I wouldn’t touch a dependency if it works like a charm and > nobody requested us to migrate to a new version. > > Why do you need to update Apache Common coded? > Not sure I agree. Why not update it? > > > — >