[GitHub] ignite pull request #2917: IGNITE-6690 DiscoverySpi: Clientmode Ignite shoul...

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

[GitHub] ignite pull request #2923: IGNITE-6690 DiscoverySpi: Clientmode Ignite shoul...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/2923 IGNITE-6690 DiscoverySpi: Clientmode Ignite should not fail on handsh… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignit

[jira] [Created] (IGNITE-6749) Illegal comparsion in NodeOrderComparator

Alexander Belyak created IGNITE-6749: Summary: Illegal comparsion in NodeOrderComparator Key: IGNITE-6749 URL: https://issues.apache.org/jira/browse/IGNITE-6749 Project: Ignite Issue Type

[GitHub] ignite pull request #2924: IGNITE-6357: Added support of multiple SQL statem...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2924 IGNITE-6357: Added support of multiple SQL statements for ODBC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-63

Re: Persistence per memory policy configuration

Igniters, I've found one more shortcoming which we missed during the review. The checkpoint page buffer is attributed to a data region, so originally it was a mistake to place the checkpoint page buffer size to the global configuration. This property should go to the data region configuration. I

[GitHub] ignite pull request #2925: IGNITE-6511: Fixed SQLGetDiagRec behaviour in ODB...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2925 IGNITE-6511: Fixed SQLGetDiagRec behaviour in ODBC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6511 Alternat

[GitHub] ignite pull request #2921: IGNITE-6705 .NET: CacheConfiguration missing prop...

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

affinity key syntax

Igniters, Please take a look at how the affinity syntax works in Google Spanner: https://stackoverflow.com/questions/46903159/can-i-have- multiple-tables-with-same-parent-in-google-spanner I find it rather nice. Perhaps we can borrow from it. D.

[jira] [Created] (IGNITE-6750) Return "wrong command" error in http rest api

Alexander Belyak created IGNITE-6750: Summary: Return "wrong command" error in http rest api Key: IGNITE-6750 URL: https://issues.apache.org/jira/browse/IGNITE-6750 Project: Ignite Issue

Re: affinity key syntax

Dima, Yes, I saw it also. But this is not about syntax only. Spanner use this information to store data efficiently - child entries a located near to their parents. We can think of it as if all related tables were logical caches inside one physical cache, sorted by the key. With this storage forma

Re: affinity key syntax

On Wed, Oct 25, 2017 at 3:32 AM, Vladimir Ozerov wrote: > Dima, > > Yes, I saw it also. But this is not about syntax only. Spanner use this > information to store data efficiently - child entries a located near to > their parents. We can think of it as if all related tables were logical > caches

Re: affinity key syntax

In Spanner once parent key is found you don't need to search for child keys from scratch - they are located just after the parent key in the tree. In Ignite child and parent keys are located in different trees, hence more lookups are needed. On Wed, Oct 25, 2017 at 1:36 PM, Dmitriy Setrakyan wrot

Re: affinity key syntax

For example, currently every table in Ignite has at least two PK indexes - one for cache operations, and another one for H2. If you have two tables (parent - child), you have either 4 indexes (if they are in different groups), or 3 indexes (same logical group). But even if certain tree is shared be

Ignite contribution and Jira access request

Hello Ignite Community! My name is Roman. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-6141. Any help on this will be appreciated. Could you please grant me access to Ignite Jira? My JIRA ID is  rkondakov. Thanks!   With best regards, Roman Kondakov

Ability to disable WAL in runtime to speed up load

Igniters, We have a ticket to implement runtime WAL state management [1].It will be possible to disable it temporarily. This is very useful for data loading case. Our experiments show that we can improve data loading time by a factor of 2x-10x depending on configuration, indexes and cluster topolo

Re: Ability to disable WAL in runtime to speed up load

One more idea - ability to create a cache with initially disabled WAL. Might be useful. On Wed, Oct 25, 2017 at 2:35 PM, Vladimir Ozerov wrote: > Igniters, > > We have a ticket to implement runtime WAL state management [1].It will be > possible to disable it temporarily. This is very useful for

Re: Ability to disable WAL in runtime to speed up load

IMO IgniteCache.disableWal() should be enough. Also what about an option to disable WAL when IgniteDataStreamer is active? On Wed, Oct 25, 2017 at 2:38 PM, Vladimir Ozerov wrote: > One more idea - ability to create a cache with initially disabled WAL. > Might be useful. > > On Wed, Oct 25, 2017

[GitHub] ignite pull request #2893: IGNITE-6555 When a CacheStore with a @SpringResou...

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

[jira] [Created] (IGNITE-6751) Skip upload ignite-dev-utils module into maven repository

Oleg Ostanin created IGNITE-6751: Summary: Skip upload ignite-dev-utils module into maven repository Key: IGNITE-6751 URL: https://issues.apache.org/jira/browse/IGNITE-6751 Project: Ignite Is

[GitHub] ignite pull request #2926: IGNITE-6751 skipped upload ignite-dev-utils modul...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2926 IGNITE-6751 skipped upload ignite-dev-utils module into maven repository You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-i

Re: Ability to disable WAL in runtime to speed up load

Pavel, This feature will work independently of streamer. If you want to load data with streamer, then you disable WAL first through some API call or SQL command, and then start loading. On Wed, Oct 25, 2017 at 2:41 PM, Pavel Tupitsyn wrote: > IMO IgniteCache.disableWal() should be enough. > > A

[GitHub] ignite pull request #2850: ignite-6572 allow multiple caches use one SQL sch...

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

[GitHub] ignite pull request #2913: Ignite 6512

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

Re: Ability to disable WAL in runtime to speed up load

I do not like boolean isWalEnabled(String... cacheNames) - it's semantics is confusing. Should it return true if WAL is enabled for all caches or if WAL is enabled for at least one cache? IMO, since this is a local-read operation, single cache per call is enough. As for the API placement, it looks

Re: Ability to disable WAL in runtime to speed up load

Vladimir, It would be useful to be able to automatically disable WAL when streaming starts and re-enable after it ends, don't you think so? Something like IgniteDataStreamer.disableWal property. This is in addition to other API calls that you suggested. On Wed, Oct 25, 2017 at 3:25 PM, Alexey G

Re: Ability to disable WAL in runtime to speed up load

Pavel, WAL disabling is a very dangerous operation and it seems to be not a good idea to allow run regular operation with .disabledWal(). Let's think twice how to make new API safe. On Wed, Oct 25, 2017 at 3:25 PM, Pavel Tupitsyn wrote: > Vladimir, > > It would be useful to be able to automatic

[jira] [Created] (IGNITE-6752) JDBC thin: connection property refactoring

Taras Ledkov created IGNITE-6752: Summary: JDBC thin: connection property refactoring Key: IGNITE-6752 URL: https://issues.apache.org/jira/browse/IGNITE-6752 Project: Ignite Issue Type: Task

Re: IGNITE-6135 java.sql.Date is serialized using OptimizedMarshaller

Hi Nikita, Sorry for the late reply. See my comments in JIRA. Thanks, Pavel On Fri, Oct 20, 2017 at 12:10 PM, Nikita Amelchev wrote: > Hello, Pavel, Igor, Igniters. > > I have implemented javax.sql.Date type for a binary protocol [1,2]. > According to TC tests [3] we need to add support for sq

[jira] [Created] (IGNITE-6753) Allow plugable page memory for testing proposes

Mikhail Cherkasov created IGNITE-6753: - Summary: Allow plugable page memory for testing proposes Key: IGNITE-6753 URL: https://issues.apache.org/jira/browse/IGNITE-6753 Project: Ignite Is

Re: Ability to disable WAL in runtime to speed up load

Alex, My bad, I meant "isWalEnabled(String cacheName)" of course. On Wed, Oct 25, 2017 at 3:34 PM, Anton Vinogradov wrote: > Pavel, > > WAL disabling is a very dangerous operation and it seems to be not a good > idea to allow run regular operation with .disabledWal(). > Let's think twice how to

Re: Ability to disable WAL in runtime to speed up load

Pavel, No, this is not the case we are trying to cover. WAL disabling should be separate operation, which is not tied to any API, whether this is streamer, cache put, or DML. On Wed, Oct 25, 2017 at 5:20 PM, Vladimir Ozerov wrote: > Alex, > > My bad, I meant "isWalEnabled(String cacheName)" of

[jira] [Created] (IGNITE-6754) Support coordinator change while sql is in progress

Semen Boikov created IGNITE-6754: Summary: Support coordinator change while sql is in progress Key: IGNITE-6754 URL: https://issues.apache.org/jira/browse/IGNITE-6754 Project: Ignite Issue Ty

[jira] [Created] (IGNITE-6755) Add possibility to create sql tables with DDL without defined PRIMARY KEY, by adding it implicitly

Evgenii Zhuravlev created IGNITE-6755: - Summary: Add possibility to create sql tables with DDL without defined PRIMARY KEY, by adding it implicitly Key: IGNITE-6755 URL: https://issues.apache.org/jira/browse/I

Re: Java 9 support

Vladimir, Thanks for performing the analysis! Yes, we should definitely roll out Java 9 support by the end of this year. — Denis > On Oct 24, 2017, at 8:19 AM, Vladimir Ozerov wrote: > > Igniters, > > I created umbrella ticket for Java 9 [1]. All known issues are aggregated > there. I propo

Re: Ability to disable WAL in runtime to speed up load

Vladimir, Several questions: 1. On which interface do you plan to add enable/disableWal()? 2. Is it possible that when enabling/disabling WAL for multiple caches, some fail and some succeed? 3. is enable/disableWal a synchronous operation? 4. What happens if a user starts streaming

Re: Use _HOST instead of FDQN when configuring principal for IgfsSecondaryFileSystem with kerberos enable

Hi Reid, thanks for the contribution! Taras, Vladimir, as IGFS maintainer could you check the PR? — Denis > On Oct 24, 2017, at 10:11 PM, C Reid wrote: > > Hi Igniters,​​ > > I file an issue about providing a more friendly way to configure kerberos > principal for kerberized hdfs. And i'm gl

Re: [DISCUSS] Ignite Update Checker

Hi Cos, Sure, will see you around there. Anyway, a short summary is the following. Starting Ignite 2.3 the nodes will be connecting to a *static* file [1] deployed on Ignite site to obtain the most recent version. If the file has a later version than the nodes will print out a message encoura

Re: Ignite contribution and Jira access request

Welcome Roman! According to JIRA you have been already added to the contributors list. *Igniters*, make sure to reply to a thread like this if you update the contributors list. Roman, as for IGNITE-6141 please share your questions or solutions in a separate discussion. — Denis > On Oct 25,

Re: Persistence per memory policy configuration

The changes are implemented in ignite-6748 branch. TC run is pending. 2017-10-25 11:26 GMT+03:00 Alexey Goncharuk : > Igniters, > > I've found one more shortcoming which we missed during the review. The > checkpoint page buffer is attributed to a data region, so originally it was > a mistake to p

[GitHub] ignite pull request #2927: IGNITE-6752 JDBC thin: connection property refact...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2927 IGNITE-6752 JDBC thin: connection property refactoring You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

Re: Ability to disable WAL in runtime to speed up load

Guys, Sever things to clarify: - disabled WAL means disabled checkpointing (no data on disk at all)? - after turning the WAL back when a preloading is over, how can I know a moment in time when the disk holds the whole copy of data so that it’s safe to restart the whole cluster? — Denis > On O

Re: Ability to disable WAL in runtime to speed up load

Denis, 1) Not necessarily. You may want to stream more data than you have memory. In this case, Ignite must spill some data to disk, and in the first phase, this will be done by the same checkpointing mechanics. In the second phase, we can implement a smarter and faster (no-COW) data spill, but st

Allow multiple caches use one SQL schema

Vladimir, Guess this has to be documented under Java Dev Guide section? https://apacheignite-sql.readme.io/docs/schema-and-indexes Do we need to do the same for .NET and C++? — Denis > Begin forwarded message: > > From: "Vladimir Oz

[GitHub] ignite pull request #2908: ignite-6654: Added IgniteOOM propagation for clie...

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

[GitHub] ignite pull request #2909: ignite-6639: TCP communication skip local node lo...

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

[GitHub] ignite pull request #2926: IGNITE-6751 skipped upload ignite-dev-utils modul...

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

[jira] [Created] (IGNITE-6756) Primary Node Change causes invalidation of GridNearCacheEntry topVer

Tim Onyschak created IGNITE-6756: Summary: Primary Node Change causes invalidation of GridNearCacheEntry topVer Key: IGNITE-6756 URL: https://issues.apache.org/jira/browse/IGNITE-6756 Project: Ignite

[jira] [Created] (IGNITE-6757) to bring serializable versions of java 8 functional interfaces

Alexandre Boudnik created IGNITE-6757: - Summary: to bring serializable versions of java 8 functional interfaces Key: IGNITE-6757 URL: https://issues.apache.org/jira/browse/IGNITE-6757 Project: Ign

serializable versions of java 8 functional interfaces

Hello, In order to use java 8 lambdas, we've developed serialized versions of a few java.util.function interfaces. I'm going to make similar improvements on IgniteClosure, IgnitePredicate, etc Take care, Alexandre "Sasha" Boudnik call me via Google Voice: 1(405) BUDNIKA 1(405) 283-6452

[GitHub] ignite pull request #2928: IGNITE-6700 Node considered as failed can cause f...

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/2928 IGNITE-6700 Node considered as failed can cause failure of others nodes Added TcpDiscoverySplitTest, updated IgniteCacheTopologySplitAbstractTest Early previous node fail with more reliable

Re: serializable versions of java 8 functional interfaces

Thanks, Alex, this is useful. Is there a Jira ticket for it? If not, can you create one? On Wed, Oct 25, 2017 at 12:05 PM, Alexandre Boudnik < alexander.boud...@gmail.com> wrote: > Hello, > > In order to use java 8 lambdas, we've developed serialized versions of a > few java.util.function interfa

Sorted index includes the cache key and the affinity key columns. Why?

Hello, Ignite adds the cache key and optionally the affinity key (if defined) as two last columns of all user-defined indexes (line 301 in H2TableDescriptor). For example, given a user index salary_idx including a single field "salary", the actual index is going to look like this: CREATE INDEX

[jira] [Created] (IGNITE-6758) Slow memory releasing while deactivation

Alexander Belyak created IGNITE-6758: Summary: Slow memory releasing while deactivation Key: IGNITE-6758 URL: https://issues.apache.org/jira/browse/IGNITE-6758 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6759) URL not using in http rest API

Alexander Belyak created IGNITE-6759: Summary: URL not using in http rest API Key: IGNITE-6759 URL: https://issues.apache.org/jira/browse/IGNITE-6759 Project: Ignite Issue Type: Bug