[jira] [Created] (IGNITE-3450) Web console: Wrong message on fail to connect to database

Vasiliy Sisko created IGNITE-3450: - Summary: Web console: Wrong message on fail to connect to database Key: IGNITE-3450 URL: https://issues.apache.org/jira/browse/IGNITE-3450 Project: Ignite

[jira] [Created] (IGNITE-3449) Web console: JDBC driver should have valid Java class validator.

Vasiliy Sisko created IGNITE-3449: - Summary: Web console: JDBC driver should have valid Java class validator. Key: IGNITE-3449 URL: https://issues.apache.org/jira/browse/IGNITE-3449 Project: Ignite

Re: Ignite 3227

Saikat, I merged your PR to master. Thanks for the contribution! 2016-07-05 16:46 GMT-07:00 Dmitriy Setrakyan : > I think we should add only 1 new method: > > long sizeLong(int partId, CachePeekMode peekMode) > > D. > > On Tue, Jul 5, 2016 at 3:24 PM, Alexander Paschenko

[GitHub] ignite pull request #815: IGNITE-3227 IgniteCache: add method to calculate s...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/815 --- 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 #859: Ignite 3414 tests

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/859 Ignite 3414 tests ignite-3414-tests, PRQ for tests . You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #858: Ignite 3413

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

Re: IGNITE-2795

I've updated the fix. Currently all the copying is performed inside query iterators only if needed. 2016-07-07 14:38 GMT+03:00 Alexei Scherbakov : > Denis, > > I think the current state of fix for SQL queries is consistent with the > highlighted topics, except > >

Implement collecting what SQL statements executed on cluster and their metrics.

Hi, All! I'm working on issue "Implement collecting what SQL statements executed on cluster and their metrics" [1] For now I'm investigating code and have following questions: 1) We have different types of queries: GridCacheQueryType: SPI, SCAN, SQL, SQL_FIELDS, TEXT, SET Should I implement

Re: ignite-2310

Igniters, The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated with comment about the changes at the IgniteCompute. Please comment the ticket. The changed javadoc of the affinityRun/Call is available to review at the branch

Re: IGNITE-2795

Denis, I think the current state of fix for SQL queries is consistent with the highlighted topics, except - server node mustn’t create a copy if a result set will be transferred to a remote node; I afraid it would be difficult to implement without interfering with current implementation too

Re: ignite-2310

Taras, it is very difficult to review API changes this way. Can you please provide additional APIs in the ticket? Also, we should add documentation about reserving partitions as well. To my knowledge, this feature ensures that a partition will not be migrated while affinityRun/Call is executed,

Re: IGNITE-2795

I would say that, yes, we should make copyOnRead flag consistent across all cache ‘get’ like operations. However we need to make sure that the copy is not created in the following cases - server node mustn’t create a copy if a result set will be transferred to a remote node; - client node or

[GitHub] ignite pull request #857: Ignite 2310 Lock cache partition for affinityRun/a...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/857 Ignite 2310 Lock cache partition for affinityRun/affinityCall execution You can merge this pull request into a Git repository by running: $ git pull

Re: ignite-2310

Igniters, Please take a look at the next proposal of changes at IgniteCompute.affinityRun / affinityCall: https://github.com/gridgain/apache-ignite/commit/c57f009c44e07240fc8c8e6feed3271c63f31664#diff-b276b8e6e14915f9e5f2f5daeeddec8a So, two methods is added affinityRun and affinityCall.

IGNITE-2795

Igniters, I implemented a fix for copy-on-read semantics for cache objects returned from SQL queries and need a review. See the issue for details on PR. While developing a fix I also noticed the same bug in local cache iterators. To make a

[jira] [Created] (IGNITE-3447) put/get value by AffinityKey

Ranger Tsao created IGNITE-3447: --- Summary: put/get value by AffinityKey Key: IGNITE-3447 URL: https://issues.apache.org/jira/browse/IGNITE-3447 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3446) Visor CMD: improve usability for batch mode

Alexey Kuznetsov created IGNITE-3446: Summary: Visor CMD: improve usability for batch mode Key: IGNITE-3446 URL: https://issues.apache.org/jira/browse/IGNITE-3446 Project: Ignite Issue

[jira] [Created] (IGNITE-3445) Web console: Invalid message on save of profile.

Vasiliy Sisko created IGNITE-3445: - Summary: Web console: Invalid message on save of profile. Key: IGNITE-3445 URL: https://issues.apache.org/jira/browse/IGNITE-3445 Project: Ignite Issue