[jira] [Created] (IGNITE-6582) JDBC thin: supports 'updatedOnServer' connection flag

Taras Ledkov created IGNITE-6582: Summary: JDBC thin: supports 'updatedOnServer' connection flag Key: IGNITE-6582 URL: https://issues.apache.org/jira/browse/IGNITE-6582 Project: Ignite Issue

[GitHub] ignite pull request #2806: IGNITE-6483 Tests for availability of metrics in ...

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

[GitHub] ignite pull request #2822: proper getters for rebalance metrics were added

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2822 proper getters for rebalance metrics were added …tyle getters (without get) were deprecated You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2725: IGNITE-6397 .NET: Thin client: basic cache operat...

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

[jira] [Created] (IGNITE-6581) clent deadlock in spiStart

Konstantin Dudkov created IGNITE-6581: - Summary: clent deadlock in spiStart Key: IGNITE-6581 URL: https://issues.apache.org/jira/browse/IGNITE-6581 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6583) Methods of rebalancing progress metrics must obey JavaBean naming conventions

Sergey Chugunov created IGNITE-6583: --- Summary: Methods of rebalancing progress metrics must obey JavaBean naming conventions Key: IGNITE-6583 URL: https://issues.apache.org/jira/browse/IGNITE-6583

Re: Adding sqlline tool to Apache Ignite project

Another build with sqlline included: https://ci.ignite.apache.org/viewLog.html?buildId=881120=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda wrote: > No more doubts

[jira] [Created] (IGNITE-6584) .NET: Propagate new cache metrics

Pavel Tupitsyn created IGNITE-6584: -- Summary: .NET: Propagate new cache metrics Key: IGNITE-6584 URL: https://issues.apache.org/jira/browse/IGNITE-6584 Project: Ignite Issue Type:

Re: Adding sqlline tool to Apache Ignite project

I think it’s a must have for the ticket resolution. Denis On Monday, October 9, 2017, Anton Vinogradov wrote: > Any plans to have ignitesql.bat? > > On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin > wrote: > > > Another build with

[GitHub] ignite pull request #2823: IGNITE-6569 Exception on DROP TABLE via cache API...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2823 IGNITE-6569 Exception on DROP TABLE via cache API of cache being dropped You can merge this pull request into a Git repository by running: $ git pull

Re: Adding sqlline tool to Apache Ignite project

Any plans to have ignitesql.bat? On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin wrote: > Another build with sqlline included: > https://ci.ignite.apache.org/viewLog.html?buildId=881120; > tab=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3Pre >

Download links on ignite.apache.org not always working

Hello Igniters, It came to my attention that I am offered to download http://mirror.linux-ia64.org/apache//ignite/2.2.0/apache-ignite-fabric-2.2.0-bin.zip This links look fishy to me, and it doesn't work anyway, unable to connect. Can we please at least kick mirror.linux-ia64.org from the list

[jira] [Created] (IGNITE-6585) SVM for Apache Ignite ML module

Yury Babak created IGNITE-6585: -- Summary: SVM for Apache Ignite ML module Key: IGNITE-6585 URL: https://issues.apache.org/jira/browse/IGNITE-6585 Project: Ignite Issue Type: New Feature

Re: Integration of Spark and Ignite. Prototype.

Hello, guys. Which version of Spark do we want to use? 1. Currently, Ignite depends on Spark 2.1.0. * Can be run on JDK 7. * Still supported: 2.1.2 will be released soon. 2. Latest Spark version is 2.2.0. * Can be run only on JDK 8+ * Released Jul 11, 2017. * Already

Re: Adding sqlline tool to Apache Ignite project

New build with fixed argument parsing: https://ci.ignite.apache.org/viewLog.html?buildId=882282=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp On Mon, Oct 9, 2017 at 5:38 PM, Denis Magda wrote: > I think it’s a must have

Re: Download links on ignite.apache.org not always working

Ilya, I do not see this mirror in the list. Do you still see it? If yes, we can try filing an INFRA issue in JIRA. D. On Mon, Oct 9, 2017 at 10:00 AM, Ilya Kasnacheev wrote: > Hello Igniters, > > It came to my attention that I am offered to download >

Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

Because it should be possible to have two tables with the same name in different schemas. On Mon, Oct 9, 2017 at 9:21 PM, Dmitriy Setrakyan wrote: > On Mon, Oct 9, 2017 at 1:27 AM, Vladimir Ozerov > wrote: > > > Hi Dima, > > > > To maintain unique

[GitHub] ignite pull request #2823: IGNITE-6569 Exception on DROP TABLE via cache API...

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

Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

On Mon, Oct 9, 2017 at 12:05 PM, Vladimir Ozerov wrote: > Because it should be possible to have two tables with the same name in > different schemas. > Still confused. If we have multiple schemas with the same table/cache name, the schema name should be enough to identify

Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

On Mon, Oct 9, 2017 at 1:27 AM, Vladimir Ozerov wrote: > Hi Dima, > > To maintain unique cache names across the cluster. > Why not simply check for uniqueness at creation time? Why introduce some automatic prefix? > > On Mon, Oct 9, 2017 at 7:34 AM, Dmitriy Setrakyan

Re: Integration of Spark and Ignite. Prototype.

Hello, Valentin. Did you have a chance to look at my changes? Now I think I have done almost all required features. I want to make some performance test to ensure my implementation work properly with a significant amount of data. And I definitely need some feedback for my changes. 2017-10-09

[jira] [Created] (IGNITE-6578) Too many diagnostic: Found long running cache future

Alexander Belyak created IGNITE-6578: Summary: Too many diagnostic: Found long running cache future Key: IGNITE-6578 URL: https://issues.apache.org/jira/browse/IGNITE-6578 Project: Ignite

[GitHub] ignite pull request #2549: ignite-5097 BinaryMarshaller should write ints in...

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

Re: Persistence per memory policy configuration

Pavel, Sounds reasonable. I suggest to include both "data" and "configuration" to make it even more obvious: set/getDefaultDataRegionConfiguration set/getDataRegionConfigurations Best Regards, Ivan Rakov On 09.10.2017 10:51, Pavel Tupitsyn wrote: Sorry that I'm late to the party, but this

[GitHub] ignite pull request #2819: GG-12914: JDBC thin fix handshake compatibility f...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2819 GG-12914: JDBC thin fix handshake compatibility for version 2.3.0. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

Mikhail Cherkasov created IGNITE-6580: - Summary: Cluster can fail during concurrent re-balancing and cache destruction Key: IGNITE-6580 URL: https://issues.apache.org/jira/browse/IGNITE-6580

Re: Persistence per memory policy configuration

Sounds good to me. On Mon, Oct 9, 2017 at 12:35 PM, Ivan Rakov wrote: > Pavel, > > Sounds reasonable. > I suggest to include both "data" and "configuration" to make it even more > obvious: > > set/getDefaultDataRegionConfiguration > set/getDataRegionConfigurations > >

Re: Why SQL_PUBLIC is appending to Cache name while using JDBC thin driver

Hi Dima, To maintain unique cache names across the cluster. On Mon, Oct 9, 2017 at 7:34 AM, Dmitriy Setrakyan wrote: > Cross-sending to dev@ > > Why do we need to append SQL_PUBLIC_ to all table names? > > D. > > -- Forwarded message -- > From: Denis

[GitHub] ignite pull request #2818: IGNITE-6380 Reject compute task execution if dead...

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/2818 IGNITE-6380 Reject compute task execution if deadlock possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-6380

[GitHub] ignite pull request #2821: ignite-5097 BinaryMarshaller should write ints in...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2821 ignite-5097 BinaryMarshaller should write ints in "varint" encoding where it makes sense You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2820: IGNITE-6234 Initialize schemaIds to empty set if ...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2820 IGNITE-6234 Initialize schemaIds to empty set if schemas field is null during the deserialization You can merge this pull request into a Git repository by running: $ git pull

Re: Persistence per memory policy configuration

Sorry that I'm late to the party, but this looks inconsistent: DataStorageConfiguration defaultRegionConfiguration DataRegionConfiguration[] getDataRegions defaultRegionConfiguration + getRegionConfigurations - or - defaultDataRegion + getDataRegions Thoughts? On Mon, Oct 2, 2017 at 9:10 PM,

[GitHub] ignite pull request #2819: GG-12914: JDBC thin fix handshake compatibility f...

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

[jira] [Created] (IGNITE-6579) WAL history does not used when node returns to cluster again

Vladislav Pyatkov created IGNITE-6579: - Summary: WAL history does not used when node returns to cluster again Key: IGNITE-6579 URL: https://issues.apache.org/jira/browse/IGNITE-6579 Project: