[jira] [Created] (IGNITE-6326) JDBC thin: statement type mismatch error is handled incorrect

Taras Ledkov created IGNITE-6326: Summary: JDBC thin: statement type mismatch error is handled incorrect Key: IGNITE-6326 URL: https://issues.apache.org/jira/browse/IGNITE-6326 Project: Ignite

[GitHub] ignite pull request #2617: IGNITE-6288 NPE on SQL query with parameters on c...

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

How to configure new thin client connector on the server?

Igniters, As you know we are working on a new thin client protocol [1]. Core logic for base cache operations is ready, so now it is time to discuss how to configure it on the server. Things are a bit complicated here. First, we have connector configuration for our old so-called REST client, see C

[jira] [Created] (IGNITE-6327) Configuration for thin client

Vladimir Ozerov created IGNITE-6327: --- Summary: Configuration for thin client Key: IGNITE-6327 URL: https://issues.apache.org/jira/browse/IGNITE-6327 Project: Ignite Issue Type: Task

Re: How to configure new thin client connector on the server?

Renaming SqlConnectorConfiguration to ClientConnectorConfiguration seems reasonable to me. On Mon, Sep 11, 2017 at 10:28 AM, Vladimir Ozerov wrote: > Igniters, > > As you know we are working on a new thin client protocol [1]. Core logic > for base cache operations is ready, so now it is time to

Re: How to configure new thin client connector on the server?

Pavel, Note that this would not be renames, but rather copy+deprecated. Otherwise we will break compilation of existing applications. On Mon, Sep 11, 2017 at 10:32 AM, Pavel Tupitsyn wrote: > Renaming SqlConnectorConfiguration to ClientConnectorConfiguration seems > reasonable to me. > > On Mon

[GitHub] ignite pull request #2630: IGNITE-6291 JDBC thin protocol compatibility is b...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2630 IGNITE-6291 JDBC thin protocol compatibility is broken You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

Dima, You contradict yourself - vote for per-column encoding on the one hand, but telling that it is "over-architected" on the other. This is exactly what I am talking about - anything more that hard-coded cluster-wide encoding is complex. You cannot simply define per-column encoding. In addition

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

OK, here is implementation plan I propose: 1) Add global character set configuration - IgniteConfiguration.characterSet. Note, it is located in IgniteConfiguration, not BinaryConfiguration. 2) All cluster nodes must have the same character set. 3) Once defined, character set cannot be changed ever.

Re: Check Ignite build for different Java before VOTE

Alexey Thanks for contributing! The idea is good for the improving of product quality. Could you explain which values the release engineer should put in the parameters section? On Wed, Sep 6, 2017 at 10:29 PM, Aleksey Chetaev wrote: > Dmitriy, > Sorry, we had problem on Ignite TeamCity, I fixe

[jira] [Created] (IGNITE-6328) in ML examples, class ExampleMatrixStorage doesn't compile

Oleg Ignatenko created IGNITE-6328: -- Summary: in ML examples, class ExampleMatrixStorage doesn't compile Key: IGNITE-6328 URL: https://issues.apache.org/jira/browse/IGNITE-6328 Project: Ignite

[GitHub] ignite pull request #2631: IGNITE-6326 JDBC thin: statement type mismatch er...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2631 IGNITE-6326 JDBC thin: statement type mismatch error is handled incorrect You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/ap

[jira] [Created] (IGNITE-6329) add Teamcity task to verify the build of ml examples

Oleg Ignatenko created IGNITE-6329: -- Summary: add Teamcity task to verify the build of ml examples Key: IGNITE-6329 URL: https://issues.apache.org/jira/browse/IGNITE-6329 Project: Ignite Iss

[GitHub] ignite pull request #2630: IGNITE-6291 JDBC thin protocol compatibility is b...

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

Re: NPE from service processor

I can only say that recent changes introduced by IGNITE-5145 in GridServiceProcessor shouldn't have changed this behavior in any way. It must be somehow connected with a lifecycle of IgniteKernal and other components. A reproducing example would h

[GitHub] ignite pull request #2632: IGNTIE-6328: in ML examples, class ExampleMatrixS...

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/2632 IGNTIE-6328: in ML examples, class ExampleMatrixStorage doesn't compile fixed DistributedRegressionExample and ExampleMatrixStorage You can merge this pull request into a Git repository by running:

[jira] [Created] (IGNITE-6330) Thin clients: close query cursors on disconnect

Pavel Tupitsyn created IGNITE-6330: -- Summary: Thin clients: close query cursors on disconnect Key: IGNITE-6330 URL: https://issues.apache.org/jira/browse/IGNITE-6330 Project: Ignite Issue Ty

[jira] [Created] (IGNITE-6331) SQL: GridH2KeyValueRowOffheap is not used

Vladimir Ozerov created IGNITE-6331: --- Summary: SQL: GridH2KeyValueRowOffheap is not used Key: IGNITE-6331 URL: https://issues.apache.org/jira/browse/IGNITE-6331 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6332) BinaryObject model replace() in client/server topology fails with ClassNotFoundFunction

Andrew Mashenkov created IGNITE-6332: Summary: BinaryObject model replace() in client/server topology fails with ClassNotFoundFunction Key: IGNITE-6332 URL: https://issues.apache.org/jira/browse/IGNITE-6332

[jira] [Created] (IGNITE-6333) Improve cache transaction metrics to understand transactions efficiency.

Alexei Scherbakov created IGNITE-6333: - Summary: Improve cache transaction metrics to understand transactions efficiency. Key: IGNITE-6333 URL: https://issues.apache.org/jira/browse/IGNITE-6333 Pr

[GitHub] ignite pull request #2633: IGNITE-6331

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

Re: BinaryObject model replace() in client/server topology fails with ClassNotFoundFunction

Crossposting to dev list. Guys, Do we have any ETA for next releases? I see no dates on release page [1]. [1] https://issues.apache.org/jira/projects/IGNITE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page On Mon, Sep 11, 2017 at 2:00 PM, Andrey Mashenkov < andrey.mashen...@gmai

Start contributing to Apache Ignite

Hello, I would like to start contributing to Ignite. This issue seems suitable for me https://issues.apache.org/jira/browse/IGNITE-6284 Can I get permissions to assign issues to myself? My username at issues.apache.org is mlipkovich Full name is Mikhail Lipkovich Thanks, Mikhail

[GitHub] ignite pull request #2634: For testing only.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2634 For testing only. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.5-5549 Alternatively you can review and a

[jira] [Created] (IGNITE-6334) Throttle writing threads during ongoing checkpoint with token bucket algorithm

Ivan Rakov created IGNITE-6334: -- Summary: Throttle writing threads during ongoing checkpoint with token bucket algorithm Key: IGNITE-6334 URL: https://issues.apache.org/jira/browse/IGNITE-6334 Project: I

[jira] [Created] (IGNITE-6335) .NET: Thin client: cache binary mode

Pavel Tupitsyn created IGNITE-6335: -- Summary: .NET: Thin client: cache binary mode Key: IGNITE-6335 URL: https://issues.apache.org/jira/browse/IGNITE-6335 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6336) .NET: Thin client: Create cache

Pavel Tupitsyn created IGNITE-6336: -- Summary: .NET: Thin client: Create cache Key: IGNITE-6336 URL: https://issues.apache.org/jira/browse/IGNITE-6336 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6337) .NET: Thin client: SQL queries

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

[jira] [Created] (IGNITE-6338) .NET: Thin client: LINQ

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

[VOTE] Apache Ignite 2.2.0 RC1

Igniters, We have uploaded a 2.2.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc1/ Git tag name is 2.2.0-rc1 This release includes the following changes: Ignite: * Checkpointing algorithm optimized * Default max memory size changed from 80% to 20% Ignite CPP: * No

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 2017-09-11 16:31 GMT+03:00 Anton Vinogradov : > Igniters, > > We have uploaded a 2.2.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc1/ > > Git tag name is > 2.2.0-rc1 > > This release includes the following changes: > > Ignite: > * Checkpointing algorithm optimi

[jira] [Created] (IGNITE-6339) WAL: Avoid closed by interruption exception when user thread is interrupted

Andrey Gura created IGNITE-6339: --- Summary: WAL: Avoid closed by interruption exception when user thread is interrupted Key: IGNITE-6339 URL: https://issues.apache.org/jira/browse/IGNITE-6339 Project: Ig

[jira] [Created] (IGNITE-6340) Attempting to create the same cache from multiple threads leads to creation of client cache on server node

Ilya Lantukh created IGNITE-6340: Summary: Attempting to create the same cache from multiple threads leads to creation of client cache on server node Key: IGNITE-6340 URL: https://issues.apache.org/jira/browse/IGN

Deprecate IgniteCache.query(Query, IgniteClosure)

Igniters, We have that very strange method, which accepts transformer. It is only supported for ScanQuery and we do not have any plans to extend it in future. Let's just deprecate it and add transformer to ScanQuery directly. Thoughts?

[GitHub] ignite pull request #2635: IGNITE-6340 : Fixed creation of client cache on s...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2635 IGNITE-6340 : Fixed creation of client cache on server node. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-634

[GitHub] ignite pull request #2636: For testing.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2636 For testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.5-6340 Alternatively you can review and apply

Re: Deprecate IgniteCache.query(Query, IgniteClosure)

+1 from me as I proposed similar design in my implementation of ContinuousQueryWithTransformer [1] https://issues.apache.org/jira/browse/IGNITE-425 2017-09-11 17:13 GMT+03:00 Vladimir Ozerov : > Igniters, > > We have that very strange method, which accepts transformer. It is only > supported fo

[jira] [Created] (IGNITE-6341) WAL: Use direct IO or libaio for writer thread

Andrey Gura created IGNITE-6341: --- Summary: WAL: Use direct IO or libaio for writer thread Key: IGNITE-6341 URL: https://issues.apache.org/jira/browse/IGNITE-6341 Project: Ignite Issue Type: Imp

Re: Deprecate IgniteCache.query(Query, IgniteClosure)

On Mon, Sep 11, 2017 at 7:13 AM, Vladimir Ozerov wrote: > Igniters, > > We have that very strange method, which accepts transformer. It is only > supported for ScanQuery and we do not have any plans to extend it in > future. > > Let's just deprecate it and add transformer to ScanQuery directly. >

[GitHub] ignite pull request #2637: jdkMarshaller(String nodeName) didn't set nodeNam...

GitHub user ahumellihuk opened a pull request: https://github.com/apache/ignite/pull/2637 jdkMarshaller(String nodeName) didn't set nodeName Node name was being set on a new instance of JdkMarshaller, not the one being returned You can merge this pull request into a Git repository

[jira] [Created] (IGNITE-6342) Exchange is hanging on eviction

Eduard Shangareev created IGNITE-6342: - Summary: Exchange is hanging on eviction Key: IGNITE-6342 URL: https://issues.apache.org/jira/browse/IGNITE-6342 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6343) Index is not used properly if changing sort order.

Alexei Scherbakov created IGNITE-6343: - Summary: Index is not used properly if changing sort order. Key: IGNITE-6343 URL: https://issues.apache.org/jira/browse/IGNITE-6343 Project: Ignite

[GitHub] ignite pull request #2612: IGNITE-6282: Implemented lazy initialization of I...

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

[GitHub] ignite pull request #2601: IGNITE-6245: Implemented returning of the number ...

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

[GitHub] ignite pull request #2581: IGNITE-6188: ODBC: Fix for SQLFreeStmt(SQL_CLOSE)...

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

[GitHub] ignite pull request #2468: IGNITE-3987: ODBC: Improved error output when que...

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

[GitHub] ignite pull request #2573: IGNITE-6211: ODBC: SQLBindParameter now does not ...

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

[GitHub] ignite pull request #2543: IGNITE-6119: Added 'lazy' flag to ODBC

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

[GitHub] ignite pull request #2362: IGNITE-5621: Support BINARY and VARBINARY SQL typ...

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

[GitHub] ignite pull request #2638: IGNITE-6151: Impemented getting and setting of th...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2638 IGNITE-6151: Impemented getting and setting of the SQL_ATTR_CONNECTION_DEAD You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ign

[jira] [Created] (IGNITE-6344) AWS AMI startup.sh gets spurious error on export statment

David Harvey created IGNITE-6344: Summary: AWS AMI startup.sh gets spurious error on export statment Key: IGNITE-6344 URL: https://issues.apache.org/jira/browse/IGNITE-6344 Project: Ignite Is

Re: Deprecate IgniteCache.query(Query, IgniteClosure)

Vova, I doubt you'll be able to easily add it directly to ScanQuery because of generics. Do you have an alternative API in mind? -Val On Mon, Sep 11, 2017 at 7:32 AM, Dmitriy Setrakyan wrote: > On Mon, Sep 11, 2017 at 7:13 AM, Vladimir Ozerov > wrote: > > > Igniters, > > > > We have that very

[GitHub] ignite pull request #2639: IGNITE-6314 Tests fix.

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2639 IGNITE-6314 Tests fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6314 Alternatively you can review a

[jira] [Created] (IGNITE-6345) Wrong message about cluster activation

Evgenii Zhuravlev created IGNITE-6345: - Summary: Wrong message about cluster activation Key: IGNITE-6345 URL: https://issues.apache.org/jira/browse/IGNITE-6345 Project: Ignite Issue Type:

Specifying schema name with thin JDBC driver

Guys, Is there a way to specify default schema name when connecting to a cluster using thin JDBC driver? This seems to be possible with other versions of JDBC driver, but not with thin one. This forces users to prefix each table with cache name in all queries, which is not very usable. Do we have

Re: NPE from service processor

Well... would be nice to see a response on Stack Overflow. So far, there is silence there. D. On Mon, Sep 11, 2017 at 3:11 AM, Denis Mekhanikov wrote: > I can only say that recent changes introduced by IGNITE-5145 > in > GridServiceProcessor >

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

Vova, generally agree, but why not also support per-cache (per-table) settings? On Mon, Sep 11, 2017 at 1:16 AM, Vladimir Ozerov wrote: > OK, here is implementation plan I propose: > 1) Add global character set configuration - > IgniteConfiguration.characterSet. Note, it is located in > IgniteC

[jira] [Created] (IGNITE-6346) Distributed set does not work in REPLICATED mode

Valentin Kulichenko created IGNITE-6346: --- Summary: Distributed set does not work in REPLICATED mode Key: IGNITE-6346 URL: https://issues.apache.org/jira/browse/IGNITE-6346 Project: Ignite

Re: How to configure new thin client connector on the server?

In my opinion all clients, including JDBC, ODBC, and REST should be implemented over the same protocol and we should not have the protocol mess we have today. Vladimir, does your suggestion about ODBC and JDBC include migration to the new client? D. On Mon, Sep 11, 2017 at 12:39 AM, Vladimir Oze

AffinityKeyMapper alternatives

Guys, Some time ago we deprecated AffinityKeyMapper in favor of CacheKeyConfiguration#affinityKeyFieldName and AffinityKeyMapped annotation. While I understand the reasons why we did this, I think it's not very flexible as requires to specify the field name on node startup. First of all, CacheKey

Re: AffinityKeyMapper alternatives

On Mon, Sep 11, 2017 at 4:01 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Guys, > > Some time ago we deprecated AffinityKeyMapper in favor > of CacheKeyConfiguration#affinityKeyFieldName and AffinityKeyMapped > annotation. While I understand the reasons why we did this, I thin

Re: AffinityKeyMapper alternatives

Even if CacheKeyConfiguration is part of CacheConfiguration, the affinity key field name can be provided only on cache startup. In many cases this name can be resolved only based on the actual key instance, e.g. during first put. Per my understanding, this already works with annotation, I just prop

Re: Ignite Benchmarking page on readme.io

I’ve done the primarily review and rename the page address. That’s it: https://apacheignite.readme.io/docs/perfomance-benchmarking Prachi, please do the final review. The page is already online. — Denis > On Sep 8, 2017, at 10:40 AM,

Re: Start contributing to Apache Ignite

Mikhail, welcome! Granted you required permissions! Look forward to your contributions! — Denis > On Sep 11, 2017, at 4:33 AM, Mikhail Lipkovich > wrote: > > Hello, > > I would like to start contributing to Ignite. > This issue seems suitable for me > https://issues.apache.org/jira/browse/IG

Re: Ignite Benchmarking page on readme.io

Several comments: 1. I would place this page directly under the top Basic Concepts section 2. I would rename the link to Benchmarking (performance is assumed) 3. I would add a few benchmark runs with examples graphs there D. On Mon, Sep 11, 2017 at 5:03 PM, Denis Magda wrote: > I’ve d

Re: Ignite Benchmarking page on readme.io

1. It’s fine to have it under the current section that will include testing related documentation proposed by Yakov in other discussion thread. 2. That’s easy and makes total sense. Renamed. 3. Mikhail could you add this? — Denis > On Sep 11, 2017, at 6:01 PM, Dmitriy Setrakyan wrote: > > Se

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 (binding) Built from sources and confirmed that ML profile is recovered and its examples are running. — Denis > On Sep 11, 2017, at 6:31 AM, Anton Vinogradov wrote: > > Igniters, > > We have uploaded a 2.2.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc1/ >

Re: Ignite Benchmarking page on readme.io

On Mon, Sep 11, 2017 at 6:10 PM, Denis Magda wrote: > 1. It’s fine to have it under the current section that will include > testing related documentation proposed by Yakov in other discussion thread. > I think we should avoid having 1-page sections. They look bad. Also, benchmarking is a very co

Re: AffinityKeyMapper alternatives

On Mon, Sep 11, 2017 at 4:47 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Even if CacheKeyConfiguration is part of CacheConfiguration, the affinity > key field name can be provided only on cache startup. In many cases this > name can be resolved only based on the actual key in

[GitHub] ignite pull request #2640: IGNITE-6345: Wrong message about cluster activati...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2640 IGNITE-6345: Wrong message about cluster activation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-6345 Alternatively

[jira] [Created] (IGNITE-6347) Exception in GridDhtPartitionMap.readExternal

Alexandr Kuramshin created IGNITE-6347: -- Summary: Exception in GridDhtPartitionMap.readExternal Key: IGNITE-6347 URL: https://issues.apache.org/jira/browse/IGNITE-6347 Project: Ignite Is

Fwd: Re: When cache node switch between primary and backup any notification be received?

Cross-sending to dev@. Igniters, is it really this difficult to iterate over local partitions, or is there a simpler way? What is worse, is that I could not find a single example anywhere of how to do it. Seems like a pretty common use case. D. -- Forwarded message -- From: Dmitr

[jira] [Created] (IGNITE-6348) Web Console: Implement control for selecting and activating cluster

Alexey Kuznetsov created IGNITE-6348: Summary: Web Console: Implement control for selecting and activating cluster Key: IGNITE-6348 URL: https://issues.apache.org/jira/browse/IGNITE-6348 Project: