Re: [VOTE] Apache Ignite 2.3.0 RC1

+1 (binding) -Val On Fri, Oct 27, 2017 at 1:40 PM, Denis Magda wrote: > +1 (binding) > > Compiled from sources and ran several examples from binary distribution. > > — > Denis > > > On Oct 27, 2017, at 11:54 AM, Vladimir Ozerov > wrote: > > > >

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

Vladimir, With pleasure, here is a ticker with the reproducer: https://issues.apache.org/jira/browse/IGNITE-6785 — Denis > On Oct 24, 2017, at 5:57 AM, Vladimir Ozerov wrote: > > Denis, > > Is it possible to create a test with reproducer? I am a bit lost. > > On Tue,

[jira] [Created] (IGNITE-6785) Affinity field name forced to be upper-case

Denis Magda created IGNITE-6785: --- Summary: Affinity field name forced to be upper-case Key: IGNITE-6785 URL: https://issues.apache.org/jira/browse/IGNITE-6785 Project: Ignite Issue Type: Task

Re: [VOTE] Apache Ignite 2.3.0 RC1

+1 (binding) Compiled from sources and ran several examples from binary distribution. — Denis > On Oct 27, 2017, at 11:54 AM, Vladimir Ozerov wrote: > > Igniters, > > We have uploaded a 2.3.0 release candidate to >

[jira] [Created] (IGNITE-6784) Document cluster activation via REST protocol

Denis Magda created IGNITE-6784: --- Summary: Document cluster activation via REST protocol Key: IGNITE-6784 URL: https://issues.apache.org/jira/browse/IGNITE-6784 Project: Ignite Issue Type:

Re: Set gitter aside

Gitter channel evaporated from the Ignite site. Exhale folks... — Denis > On Oct 27, 2017, at 2:55 AM, Konstantin Dudkov wrote: > > Agree. > > IMHO we should remove link to gitter from everywhere and keep answering > there, but for questions about product usage we should ask

[VOTE] Apache Ignite 2.3.0 RC1

Igniters, We have uploaded a 2.3.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.3.0-rc1/ Git tag name is 2.3.0-rc1 This release includes the following changes: Ignite: * Ability to enable persistence per data region. * Default page size is changed to 4KB. * Ability to

Re: New Compatibility Testing Framework module in the project

Hi Vyacheslav , Igniters, I hope you don't mind I copied this description into wiki (new page): https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Tests+How+To Hope this helps new community members to easily find the info. Sincerely, Dmitriy Pavlov вт, 17 окт. 2017 г. в 18:17,

Re: IGNITE-6692 Select query on a client with unused field throws an exception.

Nikita, I am afraid this is incorrect fix, since zero is valid hash for schema. We control whether the schema is est through the flag BinaryUtils.FLAG_HAS_SCHEMA. Please try using it instead. On Fri, Oct 27, 2017 at 6:38 PM, Nikita Amelchev wrote: > Hello, Igniters! > >

[GitHub] ignite pull request #2938: IGNITE-GG-12982 Backport IGNITE-5613 into 1.8.x

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

Re: Ignite Events Remote Filter

Alexey, Yes, seems to be the case. Unsubscription happens if *local listener* returns false not remote filter. -Val On Fri, Oct 27, 2017 at 3:12 AM, Alexey Kukushkin wrote: > Also, I ran our CacheEventsExample and I confirm the remote filter is NOT > unsubscribed

[GitHub] ignite pull request #2941: ignite-6774 Java doc is broken: "LUDecomposition....

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

[GitHub] ignite pull request #2941: ignite-6774 Java doc is broken: "LUDecomposition....

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2941 ignite-6774 Java doc is broken: "LUDecomposition.java:40: warning - T… …ag @see: missing final '>'" You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6783) Create common mechanism for group training.

Artem Malykh created IGNITE-6783: Summary: Create common mechanism for group training. Key: IGNITE-6783 URL: https://issues.apache.org/jira/browse/IGNITE-6783 Project: Ignite Issue Type:

Re: Access to modifying apacheignite.readme.io

Hello Ilya, Ignite committers have a write access to the documentation. As a contributor you should use “Suggest Edits” button on a page you’d like to edit. As for IGNITE-6775, thanks for catching it! I’ve applied all the required changes. — Denis > On Oct 27, 2017, at 2:51 AM, Ilya

IGNITE-6692 Select query on a client with unused field throws an exception.

Hello, Igniters! I’ve fixed the issue where SQL query with unused fields throws an exception [1]. Description of the problem: We can build a binary object without fields in the binary object builder. If we don't add a field, SchemaId will be set to zero. When we try to read field value,

[GitHub] ignite pull request #2866: quick proof on concept impl

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

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

Andrey, In general case we do not store any values in the index. Essentially index is a sequence of so-called "links" (i.e. pointers) to real data rows, sorted in accordance with indexed column. When two rows have the same indexed value, we need to sort them somehow still. This is where key and

Fwd: Query performance against table with/out backup

Crossposting to dev. Igniters, For now we allow user to change number of backups in configuration between grid restarts with no error. An user see new configuration object from code, but see old in visor. So, if user rise number of backups between grid restarts, it will be able to start the

[jira] [Created] (IGNITE-6781) CacheConfiguration changes doen't applies after restart with persistence

Andrew Mashenkov created IGNITE-6781: Summary: CacheConfiguration changes doen't applies after restart with persistence Key: IGNITE-6781 URL: https://issues.apache.org/jira/browse/IGNITE-6781

[jira] [Created] (IGNITE-6780) .NET: Update EventsExample with IgniteConfiguration.LocalEventListeners

Irina Zaporozhtseva created IGNITE-6780: --- Summary: .NET: Update EventsExample with IgniteConfiguration.LocalEventListeners Key: IGNITE-6780 URL: https://issues.apache.org/jira/browse/IGNITE-6780

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

Hi Denis, I had short chat with Alex G. You're right, It may be a bug. I'll prepare my reproducer and add is as test. Also I will raise the ticket if count(*) will give incorrect result. Sincerely, Dmitry Pavlov пт, 27 окт. 2017 г., 1:48 Denis Magda : > Dmitriy, > > I

[jira] [Created] (IGNITE-6779) Recreate clients caches after a node join BLT

Sergey Puchnin created IGNITE-6779: -- Summary: Recreate clients caches after a node join BLT Key: IGNITE-6779 URL: https://issues.apache.org/jira/browse/IGNITE-6779 Project: Ignite Issue

[jira] [Created] (IGNITE-6778) GridCacheDatabaseSharedManager#isPersistenceEnabled used incorrectly

Alexey Goncharuk created IGNITE-6778: Summary: GridCacheDatabaseSharedManager#isPersistenceEnabled used incorrectly Key: IGNITE-6778 URL: https://issues.apache.org/jira/browse/IGNITE-6778

[GitHub] ignite pull request #2402: [IGNITE-5860] Client disconnects if server it is ...

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

[jira] [Created] (IGNITE-6777) [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testFairReentrantLockConstantTopologyChangeNonFailoverSafe

Stanilovsky Evgeny created IGNITE-6777: -- Summary: [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testFairReentrantLockConstantTopologyChangeNonFailoverSafe Key: IGNITE-6777 URL:

[jira] [Created] (IGNITE-6776) .NET: Thin client: SQL query example

Pavel Tupitsyn created IGNITE-6776: -- Summary: .NET: Thin client: SQL query example Key: IGNITE-6776 URL: https://issues.apache.org/jira/browse/IGNITE-6776 Project: Ignite Issue Type:

Re: Ignite Events Remote Filter

Also, I ran our CacheEventsExample and I confirm the remote filter is NOT unsubscribed when it returns false. So it looks like a documentation bug only. On Fri, Oct 27, 2017 at 1:10 PM, Alexey Kukushkin wrote: > Hi, > > I think it is a documentation bug. I do not

Re: Ignite Events Remote Filter

Hi, I think it is a documentation bug. I do not think remote listener will be unsubscribed if it returns false. Let's confirm with the developers community. *Ignite Developers*, We have this comment for the remoteListener argument of the IgniteEvents#remoteListen(...): rmtFilter - Filter

Re: Set gitter aside

Agree. IMHO we should remove link to gitter from everywhere and keep answering there, but for questions about product usage we should ask to ask the question in userlist. 27/10/2017 02:10, Dmitriy Setrakyan пишет: How about we continue to have the Gitter channel, but remove the link from

Please review it IGNITE-6737

Hi, I have added PR for this issue: https://issues.apache.org/jira/browse/IGNITE-6737 and this fix passed in TC. This is serious issue witch can loop nodes from cluster. -- Vladislav Pyatkov

Access to modifying apacheignite.readme.io

Hello Igniters! I would like to have write access for readme.io to address issues like https://issues.apache.org/jira/browse/IGNITE-6775 And I've also noticed some lose/loose and its/it's which I could correct. Regards, -- Ilya Kasnacheev

[jira] [Created] (IGNITE-6775) Divergent descriptions of thread pool sizes in documentation

Ilya Kasnacheev created IGNITE-6775: --- Summary: Divergent descriptions of thread pool sizes in documentation Key: IGNITE-6775 URL: https://issues.apache.org/jira/browse/IGNITE-6775 Project: Ignite

[jira] [Created] (IGNITE-6774) Java doc is broken: "LUDecomposition.java:40: warning - Tag @see: missing final '>'"

Ksenia Rybakova created IGNITE-6774: --- Summary: Java doc is broken: "LUDecomposition.java:40: warning - Tag @see: missing final '>'" Key: IGNITE-6774 URL: https://issues.apache.org/jira/browse/IGNITE-6774

[jira] [Created] (IGNITE-6773) SQL: Support TIMESTAMP_WITH_TIMEZONE data type

Pavel Tupitsyn created IGNITE-6773: -- Summary: SQL: Support TIMESTAMP_WITH_TIMEZONE data type Key: IGNITE-6773 URL: https://issues.apache.org/jira/browse/IGNITE-6773 Project: Ignite Issue

[jira] [Created] (IGNITE-6772) SQL exception messages are not descriptive

Pavel Tupitsyn created IGNITE-6772: -- Summary: SQL exception messages are not descriptive Key: IGNITE-6772 URL: https://issues.apache.org/jira/browse/IGNITE-6772 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6771) Insert query failed if kye field is present in value fields

Pavel Konstantinov created IGNITE-6771: -- Summary: Insert query failed if kye field is present in value fields Key: IGNITE-6771 URL: https://issues.apache.org/jira/browse/IGNITE-6771 Project:

[jira] [Created] (IGNITE-6770) Service proxy call should not require service class on the node

Pavel Tupitsyn created IGNITE-6770: -- Summary: Service proxy call should not require service class on the node Key: IGNITE-6770 URL: https://issues.apache.org/jira/browse/IGNITE-6770 Project: Ignite

Cache with invalid name

On creation of cache with name “\:” received exception (For MXBean after ‘\’ symbol allowed only ‘\’, ‘”’, ‘?’, ‘*’ and ‘n’ symbols): [2017-10-27 11:34:48,149][ERROR][exchange-worker-#42%tester%][CacheAffinitySharedManager] Failed to initialize cache. Will try to rollback cache start routine.

[GitHub] ignite pull request #2940: IGNITE-6769

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

[jira] [Created] (IGNITE-6769) SQL: prototype for hand-made parser

Vladimir Ozerov created IGNITE-6769: --- Summary: SQL: prototype for hand-made parser Key: IGNITE-6769 URL: https://issues.apache.org/jira/browse/IGNITE-6769 Project: Ignite Issue Type: Task