[jira] [Created] (IGNITE-6670) Web console: Check demo node configuration

Vasiliy Sisko created IGNITE-6670: - Summary: Web console: Check demo node configuration Key: IGNITE-6670 URL: https://issues.apache.org/jira/browse/IGNITE-6670 Project: Ignite Issue Type:

SQL error codes

Alex P, Vladimir, Please confirm that the error codes documented for JDBC [1] driver are shared by all SQL APIs we have. If it’s so I would create Error Codes page under SQL Reference section and will provide error handling code snippets for JDBC, ODBC and the native APIs. [1]

Re: FOR UPDATE support in SELECT clause

Vladimir, Alex P., In addition to that please review INSERT, UPDATE, DELETE, MERGE commands syntax. Are all the parameters (DIRECT, SORTED, etc.) supported by Ignite and if, yes, then how? I’m doubt that Ignite fully supports H2 syntax: https://apacheignite-sql.readme.io/v2.1/docs/dml — Denis

Re: Adding sqlline tool to Apache Ignite project

Here is the link for SQLLine documentation - https://apacheignite-sql.readme.io/v2.1/docs/sqlline -P On Tue, Oct 17, 2017 at 11:54 AM, Denis Magda wrote: > Looks good to me. Prachi will help us documenting the tool usage: > https://issues.apache.org/jira/browse/IGNITE-6656 <

FOR UPDATE support in SELECT clause

Vladimir, Igniters, I’m editing the new version of our SELECT page [1] that initially consisted of the content fully copied from H2. For instance, there we had the following statement that’s not true for Ignite: "If FOR UPDATE is specified, the tables are locked for writing. When using MVCC,

Re: Fix IgniteSpringBean in 2.x

Hi Val, SmartInitializingSingleton#afterSingletonsInstantiated is invoked right at the end of the singleton pre-instantiation phase, *with a guarantee that all regular singleton beans have been created already*. This behavior allows avoiding the deadlock case described in the first message.

[jira] [Created] (IGNITE-6669) CacheStoreSessionListener#onSessionStart() #onSessionEnd() methods are called by GridCacheStoreManagerAdapter even if a store operation should not be performed.

Vyacheslav Koptilin created IGNITE-6669: --- Summary: CacheStoreSessionListener#onSessionStart() #onSessionEnd() methods are called by GridCacheStoreManagerAdapter even if a store operation should not be performed. Key:

Re: Fix IgniteSpringBean in 2.x

Hi Alex, This indeed has to be fixed, I've seen this issue multiple times. Can you please clarify the difference between SmartInitializingSingleton and InitializingBean? And what exactly will not work if we switch? Can you give an example? -Val On Wed, Oct 18, 2017 at 8:56 AM, Alexander

Re: Integration of Spark and Ignite. Prototype.

Hello, Valentin. My answers is below. Dmitry, do we need to move discussion to Jira? > 1. Why do we have org.apache.spark.sql.ignite package in our codebase? As I mentioned earlier, to implement and override Spark Catalog one have to use internal(private) Spark API. So I have to use package

Fix IgniteSpringBean in 2.x

Hi Igniters, There is an issue that IgniteSpringBean deadlocks when there is CacheStore, Service, you name it with @SpringResource annotated fields https://issues.apache.org/jira/browse/IGNITE-6555. The issue appeared after moving the logic for starting statically configured caches to operate in

Re: Data compression in Ignite

Hi, Igniters! Are there any results of researching or a prototype of compression feature? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-6668) Binary metadata read must not block if called from discovery thread.

Sergey Chugunov created IGNITE-6668: --- Summary: Binary metadata read must not block if called from discovery thread. Key: IGNITE-6668 URL: https://issues.apache.org/jira/browse/IGNITE-6668 Project:

[jira] [Created] (IGNITE-6667) Allow discovery cache instance reuse if only minor topology change has occured.

Alexei Scherbakov created IGNITE-6667: - Summary: Allow discovery cache instance reuse if only minor topology change has occured. Key: IGNITE-6667 URL: https://issues.apache.org/jira/browse/IGNITE-6667

[GitHub] ignite pull request #2879: IGNITE-6660 fixed Python Redis example (print sta...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2879 IGNITE-6660 fixed Python Redis example (print statements) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2878: IGNITE-6666

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/2878 IGNITE- Defined the variable totalLen for TIME type in method BinaryObjectImpl.writeFieldByOrder. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6666) BinaryObjectImpl.writeFieldByOrder method does not support TIME

Amelchev Nikita created IGNITE-: --- Summary: BinaryObjectImpl.writeFieldByOrder method does not support TIME Key: IGNITE- URL: https://issues.apache.org/jira/browse/IGNITE- Project:

[jira] [Created] (IGNITE-6665) Client node re-joins only to the list from disco configuration and ignores the rest nodes

Mikhail Cherkasov created IGNITE-6665: - Summary: Client node re-joins only to the list from disco configuration and ignores the rest nodes Key: IGNITE-6665 URL:

[GitHub] ignite pull request #2869: IGNITE-1804: Test is not flaky anymore

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2869 ---

[GitHub] ignite pull request #2877: IGNITE-1804: Test is not flaky anymore

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2877 IGNITE-1804: Test is not flaky anymore You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-1804

[GitHub] ignite pull request #2876: IGNITE-6627 .NET: Fix repeated known metadata upd...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2876 IGNITE-6627 .NET: Fix repeated known metadata updates Previous commit has broken the BinaryStructureTracker optimization You can merge this pull request into a Git repository by running: $

[GitHub] ignite pull request #2875: IGNITE-6662

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

[jira] [Created] (IGNITE-6664) Memcached example refactoring

Sergey Kozlov created IGNITE-6664: - Summary: Memcached example refactoring Key: IGNITE-6664 URL: https://issues.apache.org/jira/browse/IGNITE-6664 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2861: Ignite 5608

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

[jira] [Created] (IGNITE-6663) SQL: optimize primary key equality lookup

Vladimir Ozerov created IGNITE-6663: --- Summary: SQL: optimize primary key equality lookup Key: IGNITE-6663 URL: https://issues.apache.org/jira/browse/IGNITE-6663 Project: Ignite Issue Type:

[GitHub] ignite pull request #2875: IGNITE-6662

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

[jira] [Created] (IGNITE-6662) SQL: affinity key column is resolved incorrectly in GridH2Table

Vladimir Ozerov created IGNITE-6662: --- Summary: SQL: affinity key column is resolved incorrectly in GridH2Table Key: IGNITE-6662 URL: https://issues.apache.org/jira/browse/IGNITE-6662 Project:

[jira] [Created] (IGNITE-6660) Python Redis example fails for python 3 run

Sergey Kozlov created IGNITE-6660: - Summary: Python Redis example fails for python 3 run Key: IGNITE-6660 URL: https://issues.apache.org/jira/browse/IGNITE-6660 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6661) fix client deadlock in 2.x

Konstantin Dudkov created IGNITE-6661: - Summary: fix client deadlock in 2.x Key: IGNITE-6661 URL: https://issues.apache.org/jira/browse/IGNITE-6661 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request #2874: IGNITE-6658 Add a version of Ignite instance to l...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2874 IGNITE-6658 Add a version of Ignite instance to logger category You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-6658

[jira] [Created] (IGNITE-6659) Check that public API is not called in sensitive system threads

Alexey Goncharuk created IGNITE-6659: Summary: Check that public API is not called in sensitive system threads Key: IGNITE-6659 URL: https://issues.apache.org/jira/browse/IGNITE-6659 Project:

[jira] [Created] (IGNITE-6658) Add a version of Ignite instance to logger category

Vyacheslav Daradur created IGNITE-6658: -- Summary: Add a version of Ignite instance to logger category Key: IGNITE-6658 URL: https://issues.apache.org/jira/browse/IGNITE-6658 Project: Ignite