[jira] [Created] (IGNITE-7383) Failed to restore memory after cluster restart and activating from outdated node

Alexandr Kuramshin created IGNITE-7383: -- Summary: Failed to restore memory after cluster restart and activating from outdated node Key: IGNITE-7383 URL: https://issues.apache.org/jira/browse/IGNITE-7383

[jira] [Created] (IGNITE-7382) Unknown Pair exception if work directory is removed after cluster shutdown

Sunny Chan created IGNITE-7382: -- Summary: Unknown Pair exception if work directory is removed after cluster shutdown Key: IGNITE-7382 URL: https://issues.apache.org/jira/browse/IGNITE-7382 Project:

[jira] [Created] (IGNITE-7381) visorcmd: improve output of 'modify' command - show Value Class info

Pavel Konstantinov created IGNITE-7381: -- Summary: visorcmd: improve output of 'modify' command - show Value Class info Key: IGNITE-7381 URL: https://issues.apache.org/jira/browse/IGNITE-7381

Re: Los Angeles Area Apache Ignite/Kubernetes Meetup

cross-posting to the user list > On Jan 10, 2018, at 3:17 PM, Dani Traphagen wrote: > > Hi everyone, > > > *January 31st *I will be speaking in Los Angeles at *Verizon Digital Media > Services* on using Apache Ignite with Kubernetes! > > > You can read all the meetup

Los Angeles Area Apache Ignite/Kubernetes Meetup

Hi everyone, *January 31st *I will be speaking in Los Angeles at *Verizon Digital Media Services* on using Apache Ignite with Kubernetes! You can read all the meetup details here along with the abstract description. Free

[GitHub] ignite pull request #3356: IGNITE-7126: add new cache metrics parameters

GitHub user AlexeyRokhin opened a pull request: https://github.com/apache/ignite/pull/3356 IGNITE-7126: add new cache metrics parameters Required parameters were added. You can merge this pull request into a Git repository by running: $ git pull

Re: DiscoverySpi based on Apache ZooKeeper

Vladimir, I wish I could be more helpful, but as I mentioned, I can't remember the exact details. It had something to do with rather low level technical details of the watcher implementation in Zookeeper. Also, I never said Zookeeper doesn't provide total ordering guarantees. In fact, its

Re: Thin Client examples for documentation

Pavel, as a side note, The methods/operations Prachi is struggling with look pretty standard to me. Do you have tests for them in the code base? I mean *not* the tests you shared before where we use existing internal binary marshaller APIs but where we code every operation from scratch (what

Thin Client examples for documentation

Pavel, I am having trouble creating examples for some of the thin protocol operations. I have uploaded my project on github - https://github.com/pgarg/ignite-examples/blob/master/src/main/java/ignite/myexamples/thinclient/ThinClientExample2.java Please look into the following methods and

Re: Scala 2.10 support

From the point of build configuration — it is required to delete modules/{scalar-2.10,spark-2.10,visor-console-2.10} directories and corresponding modules from pom.xml (they are currently disabled in ignite-6730). From the point of project operability and consistency — I’ve started this

Re: Irrelevant data in discovery messages

Absolutely agree. I thought we could already filter out system and environment properties on startup via configuration. I think it was implemented by Yakov a long time ago. Yakov Zhdanov, can you please chime in? ( Denis, the information you mention is static and does not change. It would be

Re: Scala 2.10 support

I agree that we should drop it, I just want to understand how difficult it is. What is the amount of effort associated with this change? On Wed, Jan 10, 2018 at 10:37 AM, Petr Ivanov wrote: > As much as I see, scala-2.10, spark-2.10 and visor-console-2.10 modules > require

Re: Scala 2.10 support

As much as I see, scala-2.10, spark-2.10 and visor-console-2.10 modules require scala 2.10 by dependency, which is not going to work any way (or at least without some hacky hack) with Java 9. Considering Java 9 to be strictly 2.4+ functionality — I guess it is more or less solid approach in

[GitHub] ignite pull request #3355: Ignite 7195 hotfix

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/3355 Ignite 7195 hotfix Fix printing complex objects with multiple recursive usages of GridToStringBuilder You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3354: IGNITE-7380: Avoid updating PagePartitionCounters...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3354 IGNITE-7380: Avoid updating PagePartitionCounters in case all counters were not modified You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7380) Avoid updating CountersPageId in case all counters was not modifed

Dmitriy Pavlov created IGNITE-7380: -- Summary: Avoid updating CountersPageId in case all counters was not modifed Key: IGNITE-7380 URL: https://issues.apache.org/jira/browse/IGNITE-7380 Project:

[GitHub] ignite pull request #3332: Ignite 7217 2.3

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

[GitHub] ignite pull request #3334: Ignite 7217 2.1

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

Re: Java 9 support

Andrey, performance testing is in progress. The first, there are no significant difference in performance on Java 8. But it would be great to test performance on Java 9 also. On Wed, Jan 10, 2018 at 1:25 PM, Andrey Kuznetsov wrote: > Thanks, Petr. > > I heard of some activity

[GitHub] ignite pull request #3353: IGNITE-7191 JDBC: set socket buffer to 64k by def...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3353 IGNITE-7191 JDBC: set socket buffer to 64k by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7191

Re: Scala 2.10 support

How much of an effort will be to support scala and spark 2.10? On Wed, Jan 10, 2018 at 4:24 AM, vveider wrote: > Hi, Igniters! > > > While working on Java 9 support adaptation, came to a problem with scala > 2.10 and corresponding modules (scala-2.10, spark-2.10 and >

[jira] [Created] (IGNITE-7379) .NET: CacheConfiguration.IsSqlOnheapCacheEnabled

Pavel Tupitsyn created IGNITE-7379: -- Summary: .NET: CacheConfiguration.IsSqlOnheapCacheEnabled Key: IGNITE-7379 URL: https://issues.apache.org/jira/browse/IGNITE-7379 Project: Ignite Issue

[GitHub] ignite pull request #3352: IGNITE-7301 .NET: Baseline topology

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3352 IGNITE-7301 .NET: Baseline topology You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-7301 Alternatively you can

[GitHub] ignite pull request #3351: ignite-7352 sun.misc.SharedSecrets and sun.misc.J...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3351 ignite-7352 sun.misc.SharedSecrets and sun.misc.JavaNioAccess direct usages are removed …usages are removed You can merge this pull request into a Git repository by running: $ git pull

Re: Scala 2.10 support

+1 ср, 10 янв. 2018 г. в 17:28, Alexey Kuznetsov : > +1 > > On Wed, Jan 10, 2018 at 7:27 PM, Nikolay Izhikov > wrote: > > > +1 from me. > > > > В Ср, 10/01/2018 в 05:24 -0700, vveider пишет: > > > Hi, Igniters! > > > > > > > > > While working on

Re: Scala 2.10 support

+1 On Wed, Jan 10, 2018 at 7:27 PM, Nikolay Izhikov wrote: > +1 from me. > > В Ср, 10/01/2018 в 05:24 -0700, vveider пишет: > > Hi, Igniters! > > > > > > While working on Java 9 support adaptation, came to a problem with > > scala > > 2.10 and corresponding modules

[jira] [Created] (IGNITE-7378) WAL converter: add records statistic to WAL reader dev-util

Dmitriy Pavlov created IGNITE-7378: -- Summary: WAL converter: add records statistic to WAL reader dev-util Key: IGNITE-7378 URL: https://issues.apache.org/jira/browse/IGNITE-7378 Project: Ignite

[jira] [Created] (IGNITE-7377) Removed entry is not re-created in IgniteTxManager.lockMultiple

Semen Boikov created IGNITE-7377: Summary: Removed entry is not re-created in IgniteTxManager.lockMultiple Key: IGNITE-7377 URL: https://issues.apache.org/jira/browse/IGNITE-7377 Project: Ignite

[GitHub] ignite pull request #3350: IGNITE-7375: Right cleanup after training.

GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/3350 IGNITE-7375: Right cleanup after training. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7375

[jira] [Created] (IGNITE-7376) Document optional on-heap row cache

Taras Ledkov created IGNITE-7376: Summary: Document optional on-heap row cache Key: IGNITE-7376 URL: https://issues.apache.org/jira/browse/IGNITE-7376 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3291: IGNITE-7173 SQL: implement optional row cache

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

[jira] [Created] (IGNITE-7375) Perform right cleanup for MLPGroupUpdateTrainer

Artem Malykh created IGNITE-7375: Summary: Perform right cleanup for MLPGroupUpdateTrainer Key: IGNITE-7375 URL: https://issues.apache.org/jira/browse/IGNITE-7375 Project: Ignite Issue Type:

[GitHub] ignite pull request #3341: IGNITE-7277: override equals() & hashCode() metho...

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

[jira] [Created] (IGNITE-7374) Add 'default' as a possible value for an SQL command parameter

Kirill Shirokov created IGNITE-7374: --- Summary: Add 'default' as a possible value for an SQL command parameter Key: IGNITE-7374 URL: https://issues.apache.org/jira/browse/IGNITE-7374 Project: Ignite

Re: Scala 2.10 support

+1 from me. В Ср, 10/01/2018 в 05:24 -0700, vveider пишет: > Hi, Igniters! > > > While working on Java 9 support adaptation, came to a problem with > scala > 2.10 and corresponding modules (scala-2.10, spark-2.10 and > visor-console-2.10) which will not compile under Java 9. As I see > here [1]

Scala 2.10 support

Hi, Igniters! While working on Java 9 support adaptation, came to a problem with scala 2.10 and corresponding modules (scala-2.10, spark-2.10 and visor-console-2.10) which will not compile under Java 9. As I see here [1] scala 2.10 is already deprecated in spark 2.1.0 (and lately spark version

[GitHub] ignite pull request #3333: IGNITE-7318 .NET: Move SQL examples to Sql namesp...

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

[GitHub] ignite pull request #3349: IGNITE-7346: Enable Ignite cache events per cache

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3349 IGNITE-7346: Enable Ignite cache events per cache You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-7346

[GitHub] ignite pull request #3348: IGNITE-7203 Java 8 by default

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3348 IGNITE-7203 Java 8 by default * further improved AOP test behaviour by moving javaagent call into pom.xml .NET: Fix WindowsServiceTest - pass JVM path to the service .NET: Another attempt

Re: Java 9 support

No. We got rid of monitorEnter/monitorExit there. And ReentrantLock is supposed to be a replacement. 2018-01-10 13:49 GMT+03:00 Антон Чураев : > Andrey, do You mean https://issues.apache.org/jira/browse/IGNITE-4908? > > > -- Best regards, Andrey Kuznetsov.

Re: Java 9 support

Andrey, do You mean https://issues.apache.org/jira/browse/IGNITE-4908? 2018-01-10 13:25 GMT+03:00 Andrey Kuznetsov : > Thanks, Petr. > > I heard of some activity related to performance consequences of > ReentrantLocks in IGNITE-6736 fix. So, I'd like to get a reviewer feedback

Re: Java 9 support

Thanks, Petr. I heard of some activity related to performance consequences of ReentrantLocks in IGNITE-6736 fix. So, I'd like to get a reviewer feedback first. Andrey G., Vladimir O., is it possible to merge the fix to master? 2018-01-10 9:56 GMT+03:00 Petr Ivanov : >

[jira] [Created] (IGNITE-7373) Fix style guide violations and imprecise naming in SqlParser-related code

Kirill Shirokov created IGNITE-7373: --- Summary: Fix style guide violations and imprecise naming in SqlParser-related code Key: IGNITE-7373 URL: https://issues.apache.org/jira/browse/IGNITE-7373

[jira] [Created] (IGNITE-7372) Implement escape sequences handling in internal SQL parser

Kirill Shirokov created IGNITE-7372: --- Summary: Implement escape sequences handling in internal SQL parser Key: IGNITE-7372 URL: https://issues.apache.org/jira/browse/IGNITE-7372 Project: Ignite

[jira] [Created] (IGNITE-7371) MVCC TX Repeatable read semantic

Igor Seliverstov created IGNITE-7371: Summary: MVCC TX Repeatable read semantic Key: IGNITE-7371 URL: https://issues.apache.org/jira/browse/IGNITE-7371 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-7370) Drop test tables in each test case in H2DynamicTableSelfTest

Kirill Shirokov created IGNITE-7370: --- Summary: Drop test tables in each test case in H2DynamicTableSelfTest Key: IGNITE-7370 URL: https://issues.apache.org/jira/browse/IGNITE-7370 Project: Ignite

Re: Transaction operations using the Ignite Thin Client Protocol

Hi Denis, Yes, transactions in thin client protocol are surely very important, I think we should add them soon (in 2.5). Ticket: https://issues.apache.org/jira/browse/IGNITE-7369 And yes, server node will handle everything, client just performs TX_START, TX_COMMIT, TX_ROLLBACK operations. Pavel

[jira] [Created] (IGNITE-7369) .NET: Thin client: Transactions

Pavel Tupitsyn created IGNITE-7369: -- Summary: .NET: Thin client: Transactions Key: IGNITE-7369 URL: https://issues.apache.org/jira/browse/IGNITE-7369 Project: Ignite Issue Type: Improvement

Irrelevant data in discovery messages

Igniters, Turns out, that we are sending a lot of irrelevant information in discovery messages. Some messages contain *TcpDiscoveryNode* objects, which in turn have such attributes like *PATH, java.class.path, sun.boot.class.path, java.library.path, org.apache.ignite.jvm.args, *etc. Some of these

Re: DiscoverySpi based on Apache ZooKeeper

Andrey, Vladimir, Zookeeper does provide required ordering guarantees, but Zookeeper watcher API really does not provide functionality required for DiscoverySpi out of the box. To detect nodes join/failure we need to watch for creation/deletion of znodes, but in case if some client disconnects