Re: [DISCUSSION] Spark Data Frame through Thin Client

>From my past experience with Spark Data Frame API, the thick client approach leads to many usability problems. Ex. http://apache-ignite-users.70518.x6.nabble.com/Local-node-SEGMENTED-error-causing-node-goes-down-for-no-obvious-reason-td25061.html I think it makes a lot of sense to change to thin

Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

When user performs column and index modification operation in SQL(ex create index, drop index, add column, drop column), QueryEntity in CacheConfiguration for the modified cache is not updated. Here's my analysis QueryEntity in QuerySchema is a local copy of the original QueryEntity, so the ori

Spark dataframe API will get wrong schema if user executes add/drop column DDL

Currently, when user performs add/remove column DDL, the QueryEntity will not change. This result in Spark getting wrong schema because Spark relies on QueryEntity to construct data frame schema. In Vladimir Ozerov's reply in dev list, http://apache-ignite-developers.2346864.n4.nabble.com/Schema-

Re: Spark+Ignite SQL syntax proposal

Hi Nikolay, Could you also implement the DataFrame support for spark-2.10 module? There's still some legacy users who still uses spark 1.6, they need DataFrame feature too. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Spark+Ignite SQL syntax proposal

Hi Nikolay, Could you also implement the DataFrame support for spark-2.10 module? There's some legacy spark users still using Spark 1.6, they need the DataFrame features too. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Ignite SQL join performance

Currently the only way to join data is nested loops approach stated in this two tickets. https://issues.apache.org/jira/browse/IGNITE-6201 https://issues.apache.org/jira/browse/IGNITE-6202 So we can anticipate the SQL join performance will degrade a lot after the data size reached certain amount.

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

Hi Vladimir, What's the purpose of this ticket? Does it mean in the future Ignite will have its own SQL parser instead of H2's parser Ignite is using now? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

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

Hi Vladimir, Thanks for the reply. Is there any roadmap for this new execution engine? For example, in version 2.4 the new engine will process select commands and the rest commands will still be handled by H2. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Request to contribute

Hello Ignite community, I'd like to do an enhancement on Ignite, my JIRA id is ldzhjn. Please grant permissions. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Request to contribute

Hello Alexey, My jira id is ldz, sorry for the confusion. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Discussion: Upgrade Ignite Spark Module's Spark version to 2.3.0

Spark released its newest version 2.3.0 on Feb 28th, so I'd like to open a discussion about whether we should upgrade Ignite Spark module to to the latest version. In the release notes https://spark.apache.org/releases/spark-release-2-3-0.html, spark 2.3 introduced many useful new features and as w

How to run an Ignite node inside Intellij Idea?

I try to run an Ignite ndoe inside Intellij Idea for debug reasons. I ran the mvn clean install -Pall-java,all-scala,licenses -DskipTests command from devnotes and it completed without error. But when I try to run Ignite node from this class CommandLineStartup and selected default xml config. But I

How to turn debug log on in Intellij Idea console for ignite core module?

I tried change .level=INFO to FINE in config/java.util.logging.properties file and disable quite mode using -DIGNITE_QUIET=false, but it still didn't work and there's no DEBUG or TRACE level log in the console. Please advice me how to turn debug log on in Intellij Idea console for ignite core modul

Re: How to turn debug log on in Intellij Idea console for ignite core module?

Thanks for the reply. But your approach seems only to be working for tests in Ignite core module. What I'm looking for is a way to open DEBUG mode when starting an Ignite node from modules/core/src/main/java/org/apache/ignite/startup/cmdline/CommandLineStartup.java. -- Sent from: http://apache-

Re: [jira] [Created] (IGNITE-8595) SQL: Ability to cancel DDL operations

Hello Vladimir. >From the https://apacheignite-sql.readme.io/docs/query-cancellation, it is only possible to cancel select query in java API. So select query submitted from thin client(sqlline)/jdbc/odbc is not cancellable, is my understanding correct? -- Sent from: http://apache-ignite-devel

Re: [jira] [Created] (IGNITE-8595) SQL: Ability to cancel DDL operations

Thanks for the reply, Vladimir. Is there a ticket to track the cancel feature described by you? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: How to turn debug log on in Intellij Idea console for ignite core module?

Not yet. I tried your way, but seems it's not working. The default logger is JavaLogger when I started Ignite node from CommandLineStartup. And the ignite core module does not contain Log4JLogger so it will not load \ignite\config\ignite-log4j.xml. I tried adding the ignite-log4j module into igni

Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

scala 2.10. https://issues.apache.org/jira/browse/SPARK-19810 Also, please find the dev list discussion thread here. http://apache-ignite-developers.2346864.n4.nabble.com/Discussion-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-0-td30762.html Ray -- Sent from: http://apache-ignite

Re: Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

Hi Dmitriy, Thanks for the reply. I have resolved conflicts in PR and changed the ticket status to path available. Please review and leave comments. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

Before spark 2.3, spark is compiled using scala 2.11 and 2.10 separately. Spark-2.10 module in Ignite exists to accommodate this, it's not used anywhere else in project. Now spark 2.3 decided to remove support for scala 2.10, so we can safely remove spark-2.10 module in Ignite. It won't affect vis

Re: Ignite 2.6 emergency release suggestion

Igniters, Can you squeeze this ticket into 2.6 scope? https://issues.apache.org/jira/browse/IGNITE-8534 As ignite-spark module is relatively independent module, and there're already two users in the user list trying to use spark 2.3 with Ignite last week only. http://apache-ignite-users.70518.x6

Re: Apache Flink Sink + Ignite: Ouch! Argument is invalid

Hi Saikat, The results flink calculated before sending to sink is correct, but the results in Ignite is not correct. You can remove the sink and print the stream content to validate my point. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Apache Ignite 2.7 release

Hello, Igniters. Is there any specific reason why this ticket is removed from 2.7 scope? I think this ticket is important for both usability and performance. Without this ticket, we have to create an index manually identical to primary key if we want to use SQL query. https://issues.apache.org/ji

[jira] [Created] (IGNITE-10314) QueryEntity is not updated when column and index added or dropped

Ray created IGNITE-10314: Summary: QueryEntity is not updated when column and index added or dropped Key: IGNITE-10314 URL: https://issues.apache.org/jira/browse/IGNITE-10314 Project: Ignite Issue

[jira] [Created] (IGNITE-10356) JDBC thin driver returns wrong data type for Date and Decimal SQL type

Ray created IGNITE-10356: Summary: JDBC thin driver returns wrong data type for Date and Decimal SQL type Key: IGNITE-10356 URL: https://issues.apache.org/jira/browse/IGNITE-10356 Project: Ignite

[jira] [Created] (IGNITE-10569) Null meta information when getting meta for a customized schema cache through JDBC driver

Ray created IGNITE-10569: Summary: Null meta information when getting meta for a customized schema cache through JDBC driver Key: IGNITE-10569 URL: https://issues.apache.org/jira/browse/IGNITE-10569 Project

[jira] [Created] (IGNITE-10585) JDBC driver returns Double in column metadata for Float type

Ray created IGNITE-10585: Summary: JDBC driver returns Double in column metadata for Float type Key: IGNITE-10585 URL: https://issues.apache.org/jira/browse/IGNITE-10585 Project: Ignite Issue Type

[jira] [Created] (IGNITE-8534) Upgrade Ignite Spark Module's Spark version to 2.3.0

Ray created IGNITE-8534: --- Summary: Upgrade Ignite Spark Module's Spark version to 2.3.0 Key: IGNITE-8534 URL: https://issues.apache.org/jira/browse/IGNITE-8534 Project: Ignite Issue Type: Improv

[jira] [Created] (IGNITE-8697) Flink sink throws java.lang.IllegalArgumentException when running in flink cluster mode.

Ray created IGNITE-8697: --- Summary: Flink sink throws java.lang.IllegalArgumentException when running in flink cluster mode. Key: IGNITE-8697 URL: https://issues.apache.org/jira/browse/IGNITE-8697 Project

[jira] [Created] (IGNITE-10818) GridQueryTypeDescriptor should have cacheName and alias field

Ray Liu created IGNITE-10818: Summary: GridQueryTypeDescriptor should have cacheName and alias field Key: IGNITE-10818 URL: https://issues.apache.org/jira/browse/IGNITE-10818 Project: Ignite