[GitHub] ignite pull request #1976: IGNITE-5248: Detect a 32-bit JVM using too large ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1976 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

IGNITE-5124 is ready for review

Hello Igniters, I implemented UX improvements for MemoryMetrics and added/clarified some documentation to public API. Please find changes under pull request here , for discussions feel free to leave comments in upsource review

RE: Inefficient approach to executing remote SQL queries

Hi Val This is precisely my point: it's only a minor optimization until the point when establishing each connection takes 3-4 seconds, and we establish 32 of them in sequence. At that point it becomes a serious issue: the customer cannot run SQL queries from their development machines without

[jira] [Created] (IGNITE-5273) MemoryMetrics API improvements to be ported to .NET

Sergey Chugunov created IGNITE-5273: --- Summary: MemoryMetrics API improvements to be ported to .NET Key: IGNITE-5273 URL: https://issues.apache.org/jira/browse/IGNITE-5273 Project: Ignite

[jira] [Created] (IGNITE-5274) DLL: use schema for CREATE TABLE and DROP TABLE operations in GridQueryProcessor

Vladimir Ozerov created IGNITE-5274: --- Summary: DLL: use schema for CREATE TABLE and DROP TABLE operations in GridQueryProcessor Key: IGNITE-5274 URL: https://issues.apache.org/jira/browse/IGNITE-5274

[jira] [Created] (IGNITE-5272) Try get rid of custom discovery message for client cache start

Semen Boikov created IGNITE-5272: Summary: Try get rid of custom discovery message for client cache start Key: IGNITE-5272 URL: https://issues.apache.org/jira/browse/IGNITE-5272 Project: Ignite

[GitHub] ignite pull request #1986: IGNITE-4947: Create AI 2.0 TC suites

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1986 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: TC for master is moved to Ignite 2.0 test suite

Fantastic news, thank you guys! Though, I still see "Basic" and "Binary Object Basic" suites. Should we drop one of them as well? On Tue, May 23, 2017 at 10:20 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Igniters, > > Since we removed OptimizedMarshaller in Ignite 2.0 from the

Apache Zeppelin page on readme

I noticed the latest Apache Zeppelin integration page on readme is 1.7, but there are integrations for 1.8 and 1.9 too. Missing update? https://apacheignite-mix.readme.io/v1.7/docs/apache-zeppelin -- Roman

Re: [VOTE] Accept Contribution of Ignite Persistent Store

+1 On Tue, May 23, 2017 at 12:55 AM, Denis Magda wrote: > Igniters, > > This branch (https://github.com/apache/ignite/tree/ignite-5267) adds a > distributed and transactional Persistent Store to Apache Ignite project. > The store seamlessly integrates with Apache Ignite 2.0

Re: [jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

Hello , Prachi! I reviewed reference. Removing occurrence it was the right action, Thank you! Vadim Opolski 2017-05-23 2:19 GMT+03:00 Prachi Garg (JIRA) : > > [ https://issues.apache.org/jira/browse/IGNITE-4052?page=com. >

TC for master is moved to Ignite 2.0 test suite

Igniters, Since we removed OptimizedMarshaller in Ignite 2.0 from the PublicAPI, we had a chance to remove several unnecessary test suites from the build plan from Ignite 2.0. I pushed the changes for IGNITE-4947 ticket. From this moment you should run tests from Ignite 2.0 project, which is 14

Re: [VOTE] Accept Contribution of Ignite Persistent Store

+1 On Tue, May 23, 2017 at 8:42 AM, Semyon Boikov wrote: > +1 > > On Tue, May 23, 2017 at 12:55 AM, Denis Magda wrote: > > > Igniters, > > > > This branch (https://github.com/apache/ignite/tree/ignite-5267) adds a > > distributed and transactional

Re: TC for master is moved to Ignite 2.0 test suite

Hi, Vladimir, There is a chance that in http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview some configs are for binary + simple oblect names (no package name) tests. But if there is some suspicious link that is candidate to removal, please feel free to contact me.

[jira] [Created] (IGNITE-5281) Change "space" notion to "cacheName"

Vladimir Ozerov created IGNITE-5281: --- Summary: Change "space" notion to "cacheName" Key: IGNITE-5281 URL: https://issues.apache.org/jira/browse/IGNITE-5281 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1982: IGNITE-5252: Expose getFieldName method to SqlFie...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1982 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-5282) Pass "keepBinary" flag to SQL processor from the outside

Vladimir Ozerov created IGNITE-5282: --- Summary: Pass "keepBinary" flag to SQL processor from the outside Key: IGNITE-5282 URL: https://issues.apache.org/jira/browse/IGNITE-5282 Project: Ignite

[GitHub] ignite pull request #1995: GG-12184: gridgain-pds classes are absent in grid...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/1995 GG-12184: gridgain-pds classes are absent in gridgain.classnames.prop… Tests run for backporting GG-12184 into ignite-5267. Please, don'r merge. You can merge this pull request into a Git

[GitHub] ignite pull request #1996: Ignite-5242

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1996 Ignite-5242 DROP TABLE enabled only for caches created via SQL You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Geo spatial index

Guys, Looks like we have to move our geospatial indexes to the new approach with BPlusTree. Right now it stores data in Java heap. This is especially important because we are going to have a persistence layer donated by GridGain and obviously geo spatial indexes will not work with it at all.

[GitHub] ignite pull request #1938: IGNITE-5215: Allow user to configure memory polic...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1938 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: SqlFields query result does not expose fields metadata.

IGNITE-5252 [1] is ready for review. Sergi, would you please take a look at it? [1] https://issues.apache.org/jira/browse/IGNITE-5252 On Sat, May 20, 2017 at 7:07 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Dmitry, > > Here is a link ot ticket [1] > > [1]

[GitHub] ignite pull request #1915: IGNITE-5150: Allocated memory pages count is inco...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1915 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1936: Fixed segmented indices snapshots.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1936 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1964: IGNITE 5212 Allow custom affinity for system cach...

Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/1964 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #1991: Ignite-4947: Ignite Basic and Ignite Binary Basic...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/1991 Ignite-4947: Ignite Basic and Ignite Binary Basic suites were merged,… … Binary Basic is now empty You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1992: IGNITE-5281

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

[GitHub] ignite pull request #1997: IGNITE-4994 Restored GridH2TableSelfTest

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1997 IGNITE-4994 Restored GridH2TableSelfTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4994

Upgrade dependency to outdated Lucene 3.5.0

Hi Igniters, Ignite-indexing module has outdated dependency to apache-lucene-3.5.0, however, actual version of lucene for now is 6.5.1. Here is a ticket [1]. Store format version of 3.x is deprecated in 4.x and does not supported at all in higher versions, that cause difficulties to integrate

[GitHub] ignite pull request #1990: IGNITE-5264

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1990 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: TC for master is moved to Ignite 2.0 test suite

Hi Igniters, Please review PR with 'Binary Basic' merge into 'Basic' https://github.com/apache/ignite/pull/1991 After PR is merged it will be possible to remove snapshot dependency from ‘Run All’ to ‘Binary Basic’ and remove run configuration. Best Regards, Dmitry Pavlov PS. TC run

[GitHub] ignite pull request #1912: IGNITE-5163 JDBC Driver: implement handshake for ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1912 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-5283) Transaction recovery works incorrectly with cache store and writeThrough enabled

Andrey Gura created IGNITE-5283: --- Summary: Transaction recovery works incorrectly with cache store and writeThrough enabled Key: IGNITE-5283 URL: https://issues.apache.org/jira/browse/IGNITE-5283

Re: SqlFields query result does not expose fields metadata.

Done. Sergi 2017-05-23 13:48 GMT+03:00 Andrey Mashenkov : > IGNITE-5252 [1] is ready for review. > Sergi, would you please take a look at it? > > [1] https://issues.apache.org/jira/browse/IGNITE-5252 > > On Sat, May 20, 2017 at 7:07 PM, Andrey Mashenkov < >

[GitHub] ignite pull request #1993: IGNITE-5282

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

Re: Upgrade dependency to outdated Lucene 3.5.0

Lucene6 requires JDK8 and later versions, and I think it might be reasonable to update to the Lucene5.5.4 version. 在 2017/5/23 22:07, Andrey Mashenkov 写道: Hi Igniters, Ignite-indexing module has outdated dependency to apache-lucene-3.5.0, however, actual version of lucene for now is 6.5.1.

IGNITE-532 ready for review

Hi guys! Review please - https://github.com/apache/ignite/pull/1998 https://issues.apache.org/jira/browse/IGNITE-532 I'm add Akka Stream and Akka Actor integration, please see the solution. There

Re: Upgrade dependency to outdated Lucene 3.5.0

Thanks. This fact was missed in migration guide. We have dependency to lucene in our osgi module, that refer to Apache ServiceMix :: Bundles [1] . I can't see bundle for Lucene-5.5.4 in list, but there is a bundle for Lucene-5.5.2. Let's upgrade to Lucene-5.5.2. [1]

Re: Apache Zeppelin page on readme

Hi Roman, It was moved to the another documentation domain: https://apacheignite-tools.readme.io/docs/apache-zeppelin Where did you find the old reference? — Denis > On May 22, 2017, at 11:40 PM, Roman Shtykh

Re: [VOTE] Accept Contribution of Ignite Persistent Store

+1 Raul, I think everyone got confused on the process. At this point, the code has not been merged to master, and is sitting in a separate branch. I would recommend that we proceed with the vote. If the vote is declined, then we will toss the branch. I believe that once this feature is fully

[GitHub] ignite pull request #1998: IGNITE-532: Implement IgniteAkkaStreamer to strea...

GitHub user dream-x opened a pull request: https://github.com/apache/ignite/pull/1998 IGNITE-532: Implement IgniteAkkaStreamer to stream data from Akka actors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dream-x/ignite

Re: Geo spatial index

+1 This looks natural considering that we switched to the new memory architecture. Sergi, how difficult is to support this? — Denis > On May 23, 2017, at 4:25 AM, Sergi Vladykin wrote: > > Guys, > > Looks like we have to move our geospatial indexes to the new

Re: Upgrade dependency to outdated Lucene 3.5.0

Hi Andrey I see 5.5.4 in maven repository https://mvnrepository.com/artifact/org.apache.lucene/lucene-core/5.5.4 On Tue, May 23, 2017 at 6:48 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Thanks. This fact was missed in migration guide. > > We have dependency to lucene in our osgi

Re: Inefficient approach to executing remote SQL queries

Why do we turn off the connections, once established? Why not keep them open, until an endpoint explicitly closes them? On Tue, May 23, 2017 at 2:16 AM, Sergi Vladykin wrote: > Michael, > > I see your point. I think it must not be too hard to start asynchronously >

Re: IGNITE-532 ready for review

Roman, Would you mind reviewing the contribution? — Denis > On May 23, 2017, at 8:38 AM, Kozlov Maxim wrote: > > Hi guys! > > Review please - https://github.com/apache/ignite/pull/1998 > >

[jira] [Created] (IGNITE-5284) Split IgniteH2Indexing into multiple classes if possible

Vladimir Ozerov created IGNITE-5284: --- Summary: Split IgniteH2Indexing into multiple classes if possible Key: IGNITE-5284 URL: https://issues.apache.org/jira/browse/IGNITE-5284 Project: Ignite

[GitHub] ignite pull request #1992: IGNITE-5281

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1992 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Session Replication Update on spring boot platform

Hello Val, we are in the middle of the sprint so cant hijack any of our environment but would keep you posted with the timelines. Thank you for all your help, Rishi On Tue, May 23, 2017 at 2:37 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Rishi, > > It was working for

[GitHub] ignite pull request #1999: IGNITE-5284

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

Remove/deprecate CacheConfiguration.sqlEscapeAll property

Igniters, We have a property "CacheConfiguration.sqlEscapeAll". When enabled, all database objects belonging to the cache will be case-sensitive and allow special characters. Two problems here: 1) It doesn't allow me to decouple schemas from cache easily since I it force me to refer to cache

[GitHub] ignite pull request #1993: IGNITE-5282

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1993 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: IGNITE-5124 is ready for review

Sergey, Thanks, reviewed and left the notes in the upsource. — Denis > On May 23, 2017, at 1:44 AM, Sergey Chugunov > wrote: > > Hello Igniters, > > I implemented UX improvements for MemoryMetrics and added/clarified some > documentation to public API. > > Please

[jira] [Created] (IGNITE-5285) Update metrics documentation

Denis Magda created IGNITE-5285: --- Summary: Update metrics documentation Key: IGNITE-5285 URL: https://issues.apache.org/jira/browse/IGNITE-5285 Project: Ignite Issue Type: Sub-task

Re: Inefficient approach to executing remote SQL queries

The problem here is with the initial opening of connections. With a client who connects and disconnects quickly, and frequently, a 30-second plus connection time is not workable. Mike On 23 May 2017 6:51 pm, "Dmitriy Setrakyan" wrote: > Why do we turn off the

Re: Inefficient approach to executing remote SQL queries

Got it. In this case we should definitely connect concurrently, not in parallel. I set the ticket to 2.1 release. Let's see if anyone picks it up. On Tue, May 23, 2017 at 2:56 PM, Michael Griggs wrote: > The problem here is with the initial opening of connections.

Re: Apache Zeppelin page on readme

Roman, thanks for pointing out to this. > On May 23, 2017, at 6:08 PM, Roman Shtykh wrote: > > Btw, some links at https://ignite.apache.org are > broken. For instance, OSGI Support at > https://ignite.apache.org/features/datagrid.html

Re: Apache Zeppelin page on readme

Hi Denis, I was just using the drop-down to switch the versions from https://apacheignite-mix.readme.io/v1.7/docs and couldn't find it in the same subdomain. Now it's clear, thank you! Btw, some links at https://ignite.apache.org are broken. For instance, OSGI Support at

Re: Geo spatial index

It must not be too hard to implement kd-tree over b+tree [1]. Depending on level we have to compare either X or Y coordinate. I think we will even have a performance boost for spatial indexes after this change. [1] https://en.wikipedia.org/wiki/K-d_tree Sergi 2017-05-23 18:59 GMT+03:00 Denis

Re: TC for master is moved to Ignite 2.0 test suite

Yes, we can merge 'binary basic' into 'basic' with adding following tests into 'basic': o.a.i.internal.processors.cache.IgniteMarshallerCacheClassNameConflictTest -testCachePutGetClassesWithNameConflict() o.a.i.internal.processors.cache.IgniteMarshallerCacheClientRequestsMappingOnMissTest

[jira] [Created] (IGNITE-5276) JDBC: Add handler byte to protocol

Vladimir Ozerov created IGNITE-5276: --- Summary: JDBC: Add handler byte to protocol Key: IGNITE-5276 URL: https://issues.apache.org/jira/browse/IGNITE-5276 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5275) Create SQL listener configuration based on OdbcConfiguration

Vladimir Ozerov created IGNITE-5275: --- Summary: Create SQL listener configuration based on OdbcConfiguration Key: IGNITE-5275 URL: https://issues.apache.org/jira/browse/IGNITE-5275 Project: Ignite

[jira] [Created] (IGNITE-5280) SparseDistributedMatrix refactorig

Yury Babak created IGNITE-5280: -- Summary: SparseDistributedMatrix refactorig Key: IGNITE-5280 URL: https://issues.apache.org/jira/browse/IGNITE-5280 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5279) DDL: Improve test coverage for objects with different cases (upper/lower)

Vladimir Ozerov created IGNITE-5279: --- Summary: DDL: Improve test coverage for objects with different cases (upper/lower) Key: IGNITE-5279 URL: https://issues.apache.org/jira/browse/IGNITE-5279

Re: [VOTE] Accept Contribution of Ignite Persistent Store

I'm not sure what the vote is for, if the code has already been merged to the ASF repo — even if on a branch. I do accept the donation but I think the code should have remained outside the official codebase until the VOTE passed. Not sure what the rest think. On 22 May 2017 22:55, "Denis Magda"

[jira] [Created] (IGNITE-5277) Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send()

Sergi Vladykin created IGNITE-5277: -- Summary: Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send() Key: IGNITE-5277 URL: https://issues.apache.org/jira/browse/IGNITE-5277

Re: Inefficient approach to executing remote SQL queries

Michael, I see your point. I think it must not be too hard to start asynchronously establishing connections to all the needed nodes. I've created respective issue in Jira: https://issues.apache.org/jira/browse/IGNITE-5277 Sergi 2017-05-23 11:56 GMT+03:00 Michael Griggs

[GitHub] ignite pull request #1983: Ignite 4447 2

Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1983 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #1983: Ignite 4447 2

GitHub user vadopolski reopened a pull request: https://github.com/apache/ignite/pull/1983 Ignite 4447 2 Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1931: IGNITE-5175: Performance degradation using evicti...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1931 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Session Replication Update on spring boot platform

Hi Rishi, It was working for me in cluster environment after the fix [1] we discussed in previous thread [2]. The fix was included in Ignite 2.0. Can you please reattach the latest version of your app based on Ignite 2.0 and give a detailed step by step instruction on how to reproduce the issue

Re: TC for master is moved to Ignite 2.0 test suite

Pavel, Yes, these two: http://ci.ignite.apache.org/admin/editBuildParams.html?id=buildType:Ignite20Tests_IgniteBasic http://ci.ignite.apache.org/admin/editBuildParams.html?id=buildType:Ignite20Tests_IgniteBinaryBasic They both execute org.apache.ignite.testsuites.IgniteBasicTestSuite. Looks like

Re: [VOTE] Accept Contribution of Ignite Persistent Store

+1 Sergi 2017-05-23 10:20 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > +1 > > On Tue, May 23, 2017 at 8:42 AM, Semyon Boikov > wrote: > > > +1 > > > > On Tue, May 23, 2017 at 12:55 AM, Denis Magda wrote: > > > > > Igniters, > > > >

[GitHub] ignite pull request #1990: IGNITE-5264

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

Re: [VOTE] Accept Contribution of Ignite Persistent Store

+1 On Tue, May 23, 2017 at 3:23 PM, Sergi Vladykin wrote: > +1 > > Sergi > > 2017-05-23 10:20 GMT+03:00 Valentin Kulichenko < > valentin.kuliche...@gmail.com>: > > > +1 > > > > On Tue, May 23, 2017 at 8:42 AM, Semyon Boikov > > wrote: > > > > >