Re: sql documentation

On Thursday, October 19, 2017, Dmitriy Setrakyan wrote: > Denis, > > Awesome work and great contribution! > > A minor comment. Does SELECT belong under DML? Thanks for feedback! It turned out that yes, SELECT belongs to DML. Personally, I deciphered ‘M’ as

[GitHub] ignite pull request #2845: IGNITE-6519 Race in SplitAwareTopologyValidator o...

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

Re: sql documentation

Denis, Awesome work and great contribution! A minor comment. Does SELECT belong under DML? D. On Thu, Oct 19, 2017 at 6:36 PM, Denis Magda wrote: > Igniters, > > I’m glad to share that the new SQL doc is ready for proof read: > https://apacheignite-sql.readme.io/docs > >

Re: sql documentation

Igniters, I’m glad to share that the new SQL doc is ready for proof read: https://apacheignite-sql.readme.io/docs Main sections: - Overview - SQL capabilities outline and getting started guide. - SQL Reference - SQL itself with all the commands and operations. - Architecture - insights on how

Re: SQL error codes

Yes, we should document as much as we can here. Created a ticket in advance so that this is solved before 2.3 release: https://issues.apache.org/jira/browse/IGNITE-6687 — Denis > On Oct 19, 2017, at 3:51 PM, Alexander Paschenko

[jira] [Created] (IGNITE-6687) SQL Error Codes Documentation

Denis Magda created IGNITE-6687: --- Summary: SQL Error Codes Documentation Key: IGNITE-6687 URL: https://issues.apache.org/jira/browse/IGNITE-6687 Project: Ignite Issue Type: Task Security

[jira] [Created] (IGNITE-6686) Document SQL Data Types

Denis Magda created IGNITE-6686: --- Summary: Document SQL Data Types Key: IGNITE-6686 URL: https://issues.apache.org/jira/browse/IGNITE-6686 Project: Ignite Issue Type: Task Security

Re: CacheConfiguration reusage issues with EvictionPolicy enabled.

Andrey, Using factory instead of policy instance in configuration makes sense to me, I think we should do this change. As for Hadoop module issue, is it possible to do the mentioned validation after creating the policy? I think that should fix the problem. -Val On Thu, Oct 19, 2017 at 7:50 AM

Re: SQL error codes

On Thu, Oct 19, 2017 at 2:48 PM, Alexander Paschenko < apasche...@gridgain.com> wrote: > Dmitriy, > > There are Ignite specific codes, they are returned when queries are run > via Ignite API. There are no codes explicitly shared by JDBC and ODBC, > although some of them happen to be the same. >

Re: SQL error codes

On Thu, Oct 19, 2017 at 9:48 AM, Vladimir Ozerov wrote: > No, they are not re-used. SQLSTATE is JDBC/ODBC-specific thing (and both > driver types have different codes). > Vladimir, are there any error codes that come from the Ignite engine that are shared between JDBC and

Re: Ignite Durable Memory & Persistent Store introduction for developers

Hi Denis, I've updated the section in relation to your questions, please see https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-IgniteDurableMemory I’ve also moved paragraph related to page offset calculation and usage in

[GitHub] ignite pull request #2884: IGNITE-6529: fix metadata result set

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

[jira] [Created] (IGNITE-6684) Rename "ignitesql" to "sqlline"

Vladimir Ozerov created IGNITE-6684: --- Summary: Rename "ignitesql" to "sqlline" Key: IGNITE-6684 URL: https://issues.apache.org/jira/browse/IGNITE-6684 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6683) Move WAL and Checkpointing sections to separate pages

Denis Magda created IGNITE-6683: --- Summary: Move WAL and Checkpointing sections to separate pages Key: IGNITE-6683 URL: https://issues.apache.org/jira/browse/IGNITE-6683 Project: Ignite Issue

[jira] [Created] (IGNITE-6682) Document manual cluster activation feature

Denis Magda created IGNITE-6682: --- Summary: Document manual cluster activation feature Key: IGNITE-6682 URL: https://issues.apache.org/jira/browse/IGNITE-6682 Project: Ignite Issue Type: Bug

Re: Adding sqlline tool to Apache Ignite project

>> How about renaming it to "sqlline”? No objections from my side. Who will do the renaming? Please send a note once it happens so that Prachi can update the doc and screencast. Prachi, The doc looks good, thanks! Please keep an eye on the discussion and rename the script both in the docs

Re: SQL error codes

No, they are not re-used. SQLSTATE is JDBC/ODBC-specific thing (and both driver types have different codes). On Thu, Oct 19, 2017 at 7:39 PM, Denis Magda wrote: > Igor, > > Do you have them documented somewhere? Couldn’t find in the existing docs. > > Vladimir, Alex P., > >

Re: SQL error codes

Igor, Do you have them documented somewhere? Couldn’t find in the existing docs. Vladimir, Alex P., Do we reuse the error codes developed for JDBC on the native APIs side (Java, .NET, C++)? On the JDBC page we say that the codes are ANSI SQL compliant and my guess that they have to be the

[jira] [Created] (IGNITE-6681) .NET: QueryMetrics

Pavel Tupitsyn created IGNITE-6681: -- Summary: .NET: QueryMetrics Key: IGNITE-6681 URL: https://issues.apache.org/jira/browse/IGNITE-6681 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6680) .NET: QueryDetailMetrics

Pavel Tupitsyn created IGNITE-6680: -- Summary: .NET: QueryDetailMetrics Key: IGNITE-6680 URL: https://issues.apache.org/jira/browse/IGNITE-6680 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6679) Clean up some deprecated cache metrics

Sergey Puchnin created IGNITE-6679: -- Summary: Clean up some deprecated cache metrics Key: IGNITE-6679 URL: https://issues.apache.org/jira/browse/IGNITE-6679 Project: Ignite Issue Type:

[GitHub] ignite pull request #2886: IGNITE-6675 .NET: Fix ignored IgniteConfiguration...

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

[jira] [Created] (IGNITE-6678) Web agent: Implement web-agent as cluster singleton

Alexey Kuznetsov created IGNITE-6678: Summary: Web agent: Implement web-agent as cluster singleton Key: IGNITE-6678 URL: https://issues.apache.org/jira/browse/IGNITE-6678 Project: Ignite

[jira] [Created] (IGNITE-6677) Collect QueryDetailMetrics for cache-less SQL queries

Alexey Kuznetsov created IGNITE-6677: Summary: Collect QueryDetailMetrics for cache-less SQL queries Key: IGNITE-6677 URL: https://issues.apache.org/jira/browse/IGNITE-6677 Project: Ignite

[jira] [Created] (IGNITE-6676) .NET: Use FsCheck for tests

Pavel Tupitsyn created IGNITE-6676: -- Summary: .NET: Use FsCheck for tests Key: IGNITE-6676 URL: https://issues.apache.org/jira/browse/IGNITE-6676 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #2889: Ignite 1.9.8

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

[GitHub] ignite pull request #2888: Ignite 1.9.8

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

CacheConfiguration reusage issues with EvictionPolicy enabled.

Hi Igniters, I'm working on a ticket IGNITE-6649 [1] and got stuck. Currently, we allow user to set EvictionPolicy instance into configuration instead of factory. The leads to some isses when user tries to reuse EvictionPolicy instance, e.g. it doesn't clean its queue on cache stop. Seems, we

[GitHub] ignite pull request #2887: Ignite gg 12887 1.9.8

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2887 Ignite gg 12887 1.9.8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12887-1.9.8 Alternatively you

[GitHub] ignite pull request #2886: IGNITE-6675 .NET: Fix ignored IgniteConfiguration...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2886 IGNITE-6675 .NET: Fix ignored IgniteConfiguration.IgniteHome You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6675

Re: Integration of Spark and Ignite. Prototype.

Hello. > 3. IgniteCatalog vs. IgniteExternalCatalog. Why do we have two Catalog implementations and what is the difference? IgniteCatalog removed. > 5. I don't like that IgniteStrategy and IgniteOptimization have to be set manually on SQLContext each time it's createdIs there any way to

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

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

[GitHub] ignite pull request #2885: GG-12974 Don't use org.apache.spark.Logging in Ig...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/2885 GG-12974 Don't use org.apache.spark.Logging in Ignite-spark You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-6675) IGNITE_HOME is not detected automatically when using IgniteOutputCacheProvider

Irina Zaporozhtseva created IGNITE-6675: --- Summary: IGNITE_HOME is not detected automatically when using IgniteOutputCacheProvider Key: IGNITE-6675 URL: https://issues.apache.org/jira/browse/IGNITE-6675

Re: Adding sqlline tool to Apache Ignite project

On Wed, Oct 18, 2017 at 11:30 PM, Vladimir Ozerov wrote: > Igniters, > > We named the script "Ignitesql.sh" because initially we thought that it > would have additional logic. But now it is merely a thin wrapper around > sqlline which only contains classpath creation logic

[GitHub] ignite pull request #2884: IGNITE-6529: fix metadata result set

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2884 IGNITE-6529: fix metadata result set You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6529

[GitHub] ignite pull request #2883: rollbacks due to timeouts and deadlocks (TC run)

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/2883 rollbacks due to timeouts and deadlocks (TC run) You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-6333 Alternatively you can

Re: SQL error codes

Error codes are different for ODBC and JDBC. Best Regards, Igor On Thu, Oct 19, 2017 at 3:23 AM, Denis Magda wrote: > 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

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

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

[GitHub] ignite pull request #2882: IGNITE-1793

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2882 IGNITE-1793 [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes You can merge this pull request into a Git repository by running: $ git pull

Re: Adding sqlline tool to Apache Ignite project

Prachi, Seems, documentation should point to 2.3 instead of 2.1? On Thu, Oct 19, 2017 at 9:30 AM, Vladimir Ozerov wrote: > Igniters, > > We named the script "Ignitesql.sh" because initially we thought that it > would have additional logic. But now it is merely a thin

[GitHub] ignite pull request #2881: IGNITE-6111

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

[GitHub] ignite pull request #2880: metadata read must not block when called from dis...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2880 metadata read must not block when called from discovery thread …read You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6674) Document persistence per cache configuration

Alexey Goncharuk created IGNITE-6674: Summary: Document persistence per cache configuration Key: IGNITE-6674 URL: https://issues.apache.org/jira/browse/IGNITE-6674 Project: Ignite Issue

[jira] [Created] (IGNITE-6673) Document write throttling

Alexey Goncharuk created IGNITE-6673: Summary: Document write throttling Key: IGNITE-6673 URL: https://issues.apache.org/jira/browse/IGNITE-6673 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6672) Document updated node consistent ID selection

Alexey Goncharuk created IGNITE-6672: Summary: Document updated node consistent ID selection Key: IGNITE-6672 URL: https://issues.apache.org/jira/browse/IGNITE-6672 Project: Ignite Issue

[jira] [Created] (IGNITE-6671) [Web Console] Wrong java type used in generated config from DB schema

Dmitry Karachentsev created IGNITE-6671: --- Summary: [Web Console] Wrong java type used in generated config from DB schema Key: IGNITE-6671 URL: https://issues.apache.org/jira/browse/IGNITE-6671

Re: Adding sqlline tool to Apache Ignite project

Igniters, We named the script "Ignitesql.sh" because initially we thought that it would have additional logic. But now it is merely a thin wrapper around sqlline which only contains classpath creation logic and some convenient defaults. How about renaming it to "sqlline"? чт, 19 окт. 2017 г. в