Re: Clarification on DROP TABLE command needed

Hi Denis, 1) Yes, cache is destroyed and data is purged. 2) We acquire table lock, so that DML and SELECT statements will be blocked until operation is finished. Exception about missing table will be thrown afterwards. On Tue, Oct 17, 2017 at 1:40 AM, Denis Magda wrote: >

Re: Indexing fields of non-POJO cache values

Alexey G., > How these field extractors will be configured. QueryField and QueryIndex are already quite complex classes. > Adding such a closure to configuration would complicate them even further. May be we can go in "JavaScript" way and pass a string with expression that will be parsed and

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

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2866 quick proof on concept impl You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6641 Alternatively you

Re: Indexing fields of non-POJO cache values

Alexey K., looks like this will require significant changes in H2 (I cannot find anything on partial indexes there). Vladimir, any ideas? 2017-10-17 11:35 GMT+03:00 Alexey Kuznetsov : > Alexey G., > > > How these field extractors will be configured. QueryField and >

Re: Persistence per memory policy configuration

Agree with Ivan. If we implemented backward compatibility, this would be completely counterintuitive behavior, so +1 to keep the behavior as is. As for the swap path, I see nothing wrong with having it for in-memory caches. This is a simple overflow mechanism that works fine if you do not need

Wrong SQL statement

Hello, Igniters! Currently, if one try to execute `INSERT INTO t1 VALUES(...);` it will be “IgniteSQLException: Failed to parse query: INSERT INTO Person VALUES(?,?) … Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: INSERT INTO Person

Re: Indexing fields of non-POJO cache values

Alexey G., AFAIK we are going to migrate to our own parser at some point. On Tue, Oct 17, 2017 at 3:43 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Alexey K., looks like this will require significant changes in H2 (I cannot > find anything on partial indexes there). > > Vladimir,

Re: Wrong SQL statement

Hi, There is a ticket to track it: https://issues.apache.org/jira/browse/IGNITE-6111. On 17.10.2017 11:16, Иван Федотов wrote: Hello, Igniters! Currently, if one try to execute `INSERT INTO t1 VALUES(...);` it will be “IgniteSQLException: Failed to parse query: INSERT INTO Person

Re: Indexing fields of non-POJO cache values

I like this idea. In general case, this will not even require deserializing the cache value. Consider a binary tree implementation with a binary object node {val, left, right}. In this case, it is impossible to have an index of min or max, but with Andrey's suggestion, these indexes are trivially

[GitHub] ignite pull request #2532: IGNITE-5839: Unclear exception from BinaryObjectB...

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

Re: Integration of Spark and Ignite. Prototype.

Sounds awesome. I'll try to review API & tests this week. Val, Your review still required :) On Tue, Oct 17, 2017 at 2:36 PM, Николай Ижиков wrote: > Yes > > 17 окт. 2017 г. 2:34 PM пользователь "Anton Vinogradov" < > avinogra...@gridgain.com> написал: > > > Nikolay, >

[GitHub] ignite pull request #968: Ignite-3698: ODBC: LEN(string) function

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

[GitHub] ignite pull request #1037: IGNITE-3840 : Continue investigation: High memory...

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

Re: Integration of Spark and Ignite. Prototype.

Nikolay, > With Data Frame API implementation there are no requirements to have any > Ignite files on spark worker nodes. What do you mean? I see code like: spark.sparkContext.addJar(MAVEN_HOME + "/org/apache/ignite/ignite-core/2.3.0-SNAPSHOT/ignite-core-2.3.0-SNAPSHOT.jar") On Mon, Oct 16,

[GitHub] ignite pull request #2717: Ignite-gg-12717

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

[GitHub] ignite pull request #2732: Ignite-gg-12751

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

[GitHub] ignite pull request #2210: IGNITE-5593: Affinity change message leak on mass...

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

Re: Adding sqlline tool to Apache Ignite project

New example build with sqlline: https://ci.ignite.apache.org/viewLog.html?buildId=894407=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp On Wed, Oct 11, 2017 at 1:00 AM, Denis Magda wrote: > Oleg, > > Looks good to me.

Re: Integration of Spark and Ignite. Prototype.

Nikolay, So, it will be able to start regular spark and ignite clusters and, using peer classloading via spark-context, perform any DataFrame request, correct? On Tue, Oct 17, 2017 at 2:25 PM, Николай Ижиков wrote: > Hello, Anton. > > An example you provide is a path to

[GitHub] ignite pull request #2867: -gnite 2.1.7

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

[jira] [Created] (IGNITE-6648) ML javadoc is missing in 2.2 binary release

Oleg Ostanin created IGNITE-6648: Summary: ML javadoc is missing in 2.2 binary release Key: IGNITE-6648 URL: https://issues.apache.org/jira/browse/IGNITE-6648 Project: Ignite Issue

[GitHub] ignite pull request #2864: IGNITE-6627 .NET: cache deserialization fails wit...

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

[GitHub] ignite pull request #2868: IGNITE 6648

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

[GitHub] ignite pull request #2665: Ignite-gg-12773

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

Re: Integration of Spark and Ignite. Prototype.

Hello, Anton. An example you provide is a path to a master *local* file. These libraries are added to the classpath for each remote node running submitted job. Please, see documentation: http://spark.apache.org/docs/latest/api/java/org/apache/ spark/SparkContext.html#addJar(java.lang.String)

Re: Integration of Spark and Ignite. Prototype.

Yes 17 окт. 2017 г. 2:34 PM пользователь "Anton Vinogradov" < avinogra...@gridgain.com> написал: > Nikolay, > > So, it will be able to start regular spark and ignite clusters and, using > peer classloading via spark-context, perform any DataFrame request, > correct? > > On Tue, Oct 17, 2017 at

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

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

[GitHub] ignite pull request #2871: Ignite-gg-12960

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

[jira] [Created] (IGNITE-6651) Baseline includes only attributes required for affinity function

Sergey Puchnin created IGNITE-6651: -- Summary: Baseline includes only attributes required for affinity function Key: IGNITE-6651 URL: https://issues.apache.org/jira/browse/IGNITE-6651 Project: Ignite

[jira] [Created] (IGNITE-6652) Gracefully deny joins of nodes with older version when baseline topology is set up

Sergey Puchnin created IGNITE-6652: -- Summary: Gracefully deny joins of nodes with older version when baseline topology is set up Key: IGNITE-6652 URL: https://issues.apache.org/jira/browse/IGNITE-6652

[GitHub] ignite pull request #2862: IGNITE-5195 : DataStreamer remap optimization.

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

[jira] [Created] (IGNITE-6649) Add EvitionPolicy factory support in IgniteConfiguration.

Andrew Mashenkov created IGNITE-6649: Summary: Add EvitionPolicy factory support in IgniteConfiguration. Key: IGNITE-6649 URL: https://issues.apache.org/jira/browse/IGNITE-6649 Project: Ignite

Re: [Ignite 2.3 release]: Java 9 in compatibility mode

Guys, I analyzed what was done by Evgeniy Zhuravlev to make Ignite work on Java 9 (it was done long ago for Ignite 1.x): 1) We need to create two additional modules - one for Java 9 code, other for Java 7/8. Each module will contain version-specific stuff. Also we will need some additional logic

[GitHub] ignite pull request #2870: IGNITE-2766 Deterministically reopen cache after ...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2870 IGNITE-2766 Deterministically reopen cache after client reconnect. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-6650) Introduce effective storage format for baseline topology

Alexey Goncharuk created IGNITE-6650: Summary: Introduce effective storage format for baseline topology Key: IGNITE-6650 URL: https://issues.apache.org/jira/browse/IGNITE-6650 Project: Ignite

[GitHub] ignite pull request #2872: IGNITE-5195 : DataStreamer remap optimization.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2872 IGNITE-5195 : DataStreamer remap optimization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5195

New Compatibility Testing Framework module in the project

Hi, Igniters! I would like to announce new Compatibility Testing Framework module in the project. This module has been recently included in the project [1]. Framework provides an opportunity to start working with Ignite instances of previously released versions. The entire module is built on

[jira] [Created] (IGNITE-6654) Ignite client can hang in case IgniteOOM on server

Mikhail Cherkasov created IGNITE-6654: - Summary: Ignite client can hang in case IgniteOOM on server Key: IGNITE-6654 URL: https://issues.apache.org/jira/browse/IGNITE-6654 Project: Ignite

[jira] [Created] (IGNITE-6653) Check equality configuration between metasore and XML

Sergey Puchnin created IGNITE-6653: -- Summary: Check equality configuration between metasore and XML Key: IGNITE-6653 URL: https://issues.apache.org/jira/browse/IGNITE-6653 Project: Ignite

[jira] [Created] (IGNITE-6655) gracefully handle AmazonS3Exception: Slow Down in TcpDiscoveryS3IpFinder

Konstantin Dudkov created IGNITE-6655: - Summary: gracefully handle AmazonS3Exception: Slow Down in TcpDiscoveryS3IpFinder Key: IGNITE-6655 URL: https://issues.apache.org/jira/browse/IGNITE-6655

Re: ContinuousQueryWithTransformer implementation questions - 2

Hello, guys. Anton, Yakov, can you, please, share your wisdom, and make final review of IGNITE-425 Task: https://issues.apache.org/jira/browse/IGNITE-425 PR: https://github.com/apache/ignite/pull/2372 2017-09-18 18:33 GMT+03:00 Николай Ижиков : > So, resuming: > > 1) My

Re: [Ignite 2.3 release]: Java 9 in compatibility mode

Considering the scope of the work to be done it sounds reasonable to move this task to the next release. Anyway, Java 9 was released just a couple of weeks ago and it’s normal to spend some time for the code adaptation avoiding any rush. We can release the next version by the end of the year

Re: [Ignite 2.3 release]: Java 9 in compatibility mode

On Tue, Oct 17, 2017 at 9:11 AM, Denis Magda wrote: > Considering the scope of the work to be done it sounds reasonable to move > this task to the next release. Anyway, Java 9 was released just a couple of > weeks ago and it’s normal to spend some time for the code adaptation

[GitHub] ignite pull request #2873: Ignite 2.1.6.b2

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

Re: Persistence per memory policy configuration

I am now confused. Can I please ask for the final configuration again? What will it look like? On Tue, Oct 17, 2017 at 1:16 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Agree with Ivan. If we implemented backward compatibility, this would be > completely counterintuitive behavior,

Apache Ignite meetups and events around the world in October

Igniters, The next couple of weeks Ignite experts and enthusiasts are going to present the project covering various topics: https://ignite.apache.org/events.html Silicon Valley and Bay Area: - Oct 18, Meetup at the Google Headquartes driven by Val -

Re: Adding sqlline tool to Apache Ignite project

Looks good to me. Prachi will help us documenting the tool usage: https://issues.apache.org/jira/browse/IGNITE-6656 However, I can’t conceive how to see a table structure (columns and their types, indexes with names and types) using SQLLine.

Re: Clarification on DROP TABLE command needed

Vladimir, Is the cache purged synchronously or in the background? D. On Tue, Oct 17, 2017 at 12:10 AM, Vladimir Ozerov wrote: > Hi Denis, > > 1) Yes, cache is destroyed and data is purged. > 2) We acquire table lock, so that DML and SELECT statements will be blocked >

[jira] [Created] (IGNITE-6656) SQLLine Documentation

Denis Magda created IGNITE-6656: --- Summary: SQLLine Documentation Key: IGNITE-6656 URL: https://issues.apache.org/jira/browse/IGNITE-6656 Project: Ignite Issue Type: Task Security Level:

Re: Persistence per memory policy configuration

Dmitriy, Please check description of https://issues.apache.org/jira/browse/IGNITE-6030, I've updated it with actual list of properties. Best Regards, Ivan Rakov On 17.10.2017 21:46, Dmitriy Setrakyan wrote: I am now confused. Can I please ask for the final configuration again? What will it

Re: Integration of Spark and Ignite. Prototype.

Nikolay, Anton, I did a high level review of the code. First of all, impressive results! However, I have some questions/comments. 1. Why do we have org.apache.spark.sql.ignite package in our codebase? Can these classes reside under org.apache.ignite.spark instead? 2. IgniteRelationProvider

Re: Persistence per memory policy configuration

Thanks Ivan! Let's make sure that every property gets sufficient javadoc for our users to understand. We should also document this configuration on readme. On Tue, Oct 17, 2017 at 3:06 PM, Ivan Rakov wrote: > Dmitriy, > > Please check description of

Re: Integration of Spark and Ignite. Prototype.

Val, thanks for the review. Can I ask you to add the same comments to the ticket? On Tue, Oct 17, 2017 at 3:20 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Nikolay, Anton, > > I did a high level review of the code. First of all, impressive results! > However, I have some

Re: Persistence per memory policy configuration

Ivan, Please don’t forget to update all the persistence and memory pools related examples to the new configuration format. Let’s make sure non of our example prints out the class deprecated warning. Denis On Tuesday, October 17, 2017, Dmitriy Setrakyan wrote: > Thanks