[jira] [Created] (IGNITE-5435) JDBC thin: support statement close on completion

Taras Ledkov created IGNITE-5435: Summary: JDBC thin: support statement close on completion Key: IGNITE-5435 URL: https://issues.apache.org/jira/browse/IGNITE-5435 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5425) JDBC thin: support client info

Taras Ledkov created IGNITE-5425: Summary: JDBC thin: support client info Key: IGNITE-5425 URL: https://issues.apache.org/jira/browse/IGNITE-5425 Project: Ignite Issue Type: Bug

Re: place for printing info about partition distribution (IGNITE-4756)

yzhda...@gridgain.com>> Hello guys! I want to discuss and suggest some format and place for pinting info about partition distribution to log from issue https://issues.apache.org/jira/browse/IGNITE-4756 <https://issues.apache.org/jira/browse/IGNITE-4756> What do you think about

Re: Apache Ignite 2.1 scope

hare your thoughts, ideas and concerns. — Denis -- Best Regards, Vyacheslav -- Best Regards, Vyacheslav -- Taras Ledkov Mail-To: tled...@gridgain.com

[jira] [Created] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

Taras Ledkov created IGNITE-5384: Summary: JDBC Driver: implement ResultSet#getDate(int, Calendar) Key: IGNITE-5384 URL: https://issues.apache.org/jira/browse/IGNITE-5384 Project: Ignite

[jira] [Created] (IGNITE-5344) JDBC Driver: support Statement.closeOnCompletion

Taras Ledkov created IGNITE-5344: Summary: JDBC Driver: support Statement.closeOnCompletion Key: IGNITE-5344 URL: https://issues.apache.org/jira/browse/IGNITE-5344 Project: Ignite Issue Type

Re: Default SQL schema name

;DEFAULT" is reserved SQL keyword. Personally I prefer "public". Any other thoughts? Vladimir. [1] https://issues.apache.org/jira/browse/IGNITE-5320 -- Taras Ledkov Mail-To: tled...@gridgain.com

[jira] [Created] (IGNITE-5260) JDBC Driver: implement SQLWarning supportion

Taras Ledkov created IGNITE-5260: Summary: JDBC Driver: implement SQLWarning supportion Key: IGNITE-5260 URL: https://issues.apache.org/jira/browse/IGNITE-5260 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5255) JDBC Driver: support DML

Taras Ledkov created IGNITE-5255: Summary: JDBC Driver: support DML Key: IGNITE-5255 URL: https://issues.apache.org/jira/browse/IGNITE-5255 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5237) JDBC Driver: support client info

Taras Ledkov created IGNITE-5237: Summary: JDBC Driver: support client info Key: IGNITE-5237 URL: https://issues.apache.org/jira/browse/IGNITE-5237 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5236) JDBC Driver: implement Connection.isValid througn PING message

Taras Ledkov created IGNITE-5236: Summary: JDBC Driver: implement Connection.isValid througn PING message Key: IGNITE-5236 URL: https://issues.apache.org/jira/browse/IGNITE-5236 Project: Ignite

[jira] [Created] (IGNITE-5235) JDBC Driver: impelemnt prepared statement

Taras Ledkov created IGNITE-5235: Summary: JDBC Driver: impelemnt prepared statement Key: IGNITE-5235 URL: https://issues.apache.org/jira/browse/IGNITE-5235 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5234) JDBC Driver: support connection and query timeout

Taras Ledkov created IGNITE-5234: Summary: JDBC Driver: support connection and query timeout Key: IGNITE-5234 URL: https://issues.apache.org/jira/browse/IGNITE-5234 Project: Ignite Issue

[jira] [Created] (IGNITE-5233) JDBC Driver: implement metadata support

Taras Ledkov created IGNITE-5233: Summary: JDBC Driver: implement metadata support Key: IGNITE-5233 URL: https://issues.apache.org/jira/browse/IGNITE-5233 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol

Taras Ledkov created IGNITE-5176: Summary: JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol Key: IGNITE-5176 URL: https://issues.apache.org/jira/browse/IGNITE-5176

[jira] [Created] (IGNITE-5163) JDBC Driver: thin jdbc driver is based on pure TCP protocol

Taras Ledkov created IGNITE-5163: Summary: JDBC Driver: thin jdbc driver is based on pure TCP protocol Key: IGNITE-5163 URL: https://issues.apache.org/jira/browse/IGNITE-5163 Project: Ignite

[jira] [Created] (IGNITE-5128) Support queries for GridClientData

Taras Ledkov created IGNITE-5128: Summary: Support queries for GridClientData Key: IGNITE-5128 URL: https://issues.apache.org/jira/browse/IGNITE-5128 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5126) Support batches for thin client based JDBC driver

Taras Ledkov created IGNITE-5126: Summary: Support batches for thin client based JDBC driver Key: IGNITE-5126 URL: https://issues.apache.org/jira/browse/IGNITE-5126 Project: Ignite Issue

[jira] [Created] (IGNITE-5101) Stabilize IgfsSizeSelfTest

Taras Ledkov created IGNITE-5101: Summary: Stabilize IgfsSizeSelfTest Key: IGNITE-5101 URL: https://issues.apache.org/jira/browse/IGNITE-5101 Project: Ignite Issue Type: Test

[IGNITE-5036] review the changes at the ingite-cassandra-store module

Igor, I see that you are the main contributor of the ignite-cassandra-* modules. Could you please review the changes at the ingite-cassandra-store module for the issue IGNITE-5036. Please take a look at the issue: https://issues.apache.org/jira/browse/IGNITE-5036 -- Taras Ledkov Mail

Re: Introduce custom executors for compute grid

to nodes where the specific executor is configured. On 18.04.2017 18:00, Christos Erotocritou wrote: I assume its not currently possible to constrain an executor pool to be started only on a specific node? -- Taras Ledkov Mail-To: tled...@gridgain.com

Introduce custom executors for compute grid

480e-9be1-512bc320 Issue: https://issues.apache.org/jira/browse/IGNITE-4699 Please share your thoughts or ask questions. -- Taras Ledkov Mail-To: tled...@gridgain.com

[jira] [Created] (IGNITE-4956) Stabilize the test IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp

Taras Ledkov created IGNITE-4956: Summary: Stabilize the test IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp Key: IGNITE-4956 URL: https://issues.apache.org/jira/browse/IGNITE

Re: Prohibit stateful affinity (FairAffinityFunction)

ceptable. On Mon, Apr 10, 2017 at 12:43 PM, Yakov Zhdanov <yzhda...@apache.org wrote: We should have it enabled by default. --Yakov 2017-04-10 12:42 GMT+03:00 Sergi Vladykin < sergi.vlady...@gmail.com : Why wouldn't we have useBalancer always enabled? Sergi 2017-04-10 12:31 GMT+03:0

Re: Prohibit stateful affinity (FairAffinityFunction)

2.0. We have to clearly document that the same affinity function must provide the same partition assignments for all the caches. Also I know that Taras Ledkov was working on a decent stateless replacement for FairAffinity, so we should not loose anything here.

Re: Async listeners for IgniteFuture

, additional one, or maybe force user to provide his own Executor? [1] https://issues.apache.org/jira/browse/IGNITE-4477 Thanks! -Dmitry. -- Taras Ledkov Mail-To: tled...@gridgain.com

[jira] [Created] (IGNITE-4915) Remove deprecated methods at the public API

Taras Ledkov created IGNITE-4915: Summary: Remove deprecated methods at the public API Key: IGNITE-4915 URL: https://issues.apache.org/jira/browse/IGNITE-4915 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-4839) Remove CacheTypeMetadata

Taras Ledkov created IGNITE-4839: Summary: Remove CacheTypeMetadata Key: IGNITE-4839 URL: https://issues.apache.org/jira/browse/IGNITE-4839 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4827) Remove: some backward compatibility

Taras Ledkov created IGNITE-4827: Summary: Remove: some backward compatibility Key: IGNITE-4827 URL: https://issues.apache.org/jira/browse/IGNITE-4827 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4824) Remove: AffinityTask.affinityKey method

Taras Ledkov created IGNITE-4824: Summary: Remove: AffinityTask.affinityKey method Key: IGNITE-4824 URL: https://issues.apache.org/jira/browse/IGNITE-4824 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-4756) Print info about partition distribution to log

Taras Ledkov created IGNITE-4756: Summary: Print info about partition distribution to log Key: IGNITE-4756 URL: https://issues.apache.org/jira/browse/IGNITE-4756 Project: Ignite Issue Type

Re: Major release 2.0 and compilation

rmally I would leave deprecation unless there is a strong reason to remove it. Thoughts? Vladimir. -- Sergey Kozlov GridGain Systems www.gridgain.com -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Locking of partition with affinityRun/affinityCall

Denis, I've fixed javadocs for affinityRun/affinityCall. Please review the changes at the PR: https://github.com/apache/ignite/pull/1550 On 08.12.2016 12:06, Taras Ledkov wrote: Denis, The second point is absolutely correct. The rebalancing isn't blocked. The partition will not be evicted

Re: Locking of partition with affinityRun/affinityCall

Denis, Please review the javadoc of the affinity jobs. PR: https://github.com/apache/ignite/pull/1550 On 08.12.2016 12:06, Taras Ledkov wrote: Denis, The second point is absolutely correct. The rebalancing isn't blocked. The partition will not be evicted while the partition is reserved

Re: Make async API great again

Boikov <sboi...@gridgain.com> wrote: Hi Taras, Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It seems that ComputeTaskFuture is needed only for tasks? On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov <tled...@gridgain.com> wrote: Gents I've

[jira] [Created] (IGNITE-4584) Async API: Tests refactoring to use new async API

Taras Ledkov created IGNITE-4584: Summary: Async API: Tests refactoring to use new async API Key: IGNITE-4584 URL: https://issues.apache.org/jira/browse/IGNITE-4584 Project: Ignite Issue

[jira] [Created] (IGNITE-4583) Async API: Other components refactoring

Taras Ledkov created IGNITE-4583: Summary: Async API: Other components refactoring Key: IGNITE-4583 URL: https://issues.apache.org/jira/browse/IGNITE-4583 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-4582) Async API: IgniteFileSystem refactoring

Taras Ledkov created IGNITE-4582: Summary: Async API: IgniteFileSystem refactoring Key: IGNITE-4582 URL: https://issues.apache.org/jira/browse/IGNITE-4582 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-4581) Async API: IgniteCache refactoring

Taras Ledkov created IGNITE-4581: Summary: Async API: IgniteCache refactoring Key: IGNITE-4581 URL: https://issues.apache.org/jira/browse/IGNITE-4581 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4580) Async API: Refactoring IgniteCompute

Taras Ledkov created IGNITE-4580: Summary: Async API: Refactoring IgniteCompute Key: IGNITE-4580 URL: https://issues.apache.org/jira/browse/IGNITE-4580 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request #1368: IGNITE-4462: Remove grid name from HadoopIgfsEndp...

GitHub user taras-ledkov opened a pull request: https://github.com/apache/ignite/pull/1368 IGNITE-4462: Remove grid name from HadoopIgfsEndpoint You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4462

[jira] [Created] (IGNITE-4462) IGFS client must use only IGFS name for in-proc mode

Taras Ledkov created IGNITE-4462: Summary: IGFS client must use only IGFS name for in-proc mode Key: IGNITE-4462 URL: https://issues.apache.org/jira/browse/IGNITE-4462 Project: Ignite Issue

[jira] [Created] (IGNITE-4431) Default forma of the ignite log doesn't contain a data.

Taras Ledkov created IGNITE-4431: Summary: Default forma of the ignite log doesn't contain a data. Key: IGNITE-4431 URL: https://issues.apache.org/jira/browse/IGNITE-4431 Project: Ignite

Re: Locking of partition with affinityRun/affinityCall

Denis, The second point is absolutely correct. The rebalancing isn't blocked. The partition will not be evicted while the partition is reserved. I'll update javadoc ASAP. On Wed, Nov 30, 2016 at 10:23 PM, Denis Magda wrote: > Taras, > > There is a question in regards to

[jira] [Created] (IGNITE-4369) ReentranLocks hands on unlock when node is stopped.

Taras Ledkov created IGNITE-4369: Summary: ReentranLocks hands on unlock when node is stopped. Key: IGNITE-4369 URL: https://issues.apache.org/jira/browse/IGNITE-4369 Project: Ignite Issue

[jira] [Created] (IGNITE-3931) IGFS: Support direct PROXY mode invocations. Fix tests & stabilization

Taras Ledkov created IGNITE-3931: Summary: IGFS: Support direct PROXY mode invocations. Fix tests & stabilization Key: IGNITE-3931 URL: https://issues.apache.org/jira/browse/IGNITE-3931 Pro

[jira] [Created] (IGNITE-3858) IGFS: Support direct PROXY mode invocation in methods: create / append

Taras Ledkov created IGNITE-3858: Summary: IGFS: Support direct PROXY mode invocation in methods: create / append Key: IGNITE-3858 URL: https://issues.apache.org/jira/browse/IGNITE-3858 Project

[jira] [Created] (IGNITE-3857) IGFS: Support direct PROXY mode invocation in methods: listPaths / listFiles

Taras Ledkov created IGNITE-3857: Summary: IGFS: Support direct PROXY mode invocation in methods: listPaths / listFiles Key: IGNITE-3857 URL: https://issues.apache.org/jira/browse/IGNITE-3857 Project

[jira] [Created] (IGNITE-3856) IGFS: Support direct PROXY mode invocation in method: mkdirs

Taras Ledkov created IGNITE-3856: Summary: IGFS: Support direct PROXY mode invocation in method: mkdirs Key: IGNITE-3856 URL: https://issues.apache.org/jira/browse/IGNITE-3856 Project: Ignite

[jira] [Created] (IGNITE-3855) IGFS: Support direct PROXY mode invocation in method: delete

Taras Ledkov created IGNITE-3855: Summary: IGFS: Support direct PROXY mode invocation in method: delete Key: IGNITE-3855 URL: https://issues.apache.org/jira/browse/IGNITE-3855 Project: Ignite

[jira] [Created] (IGNITE-3853) IGFS: Support direct PROXY mode invocation in method: update

Taras Ledkov created IGNITE-3853: Summary: IGFS: Support direct PROXY mode invocation in method: update Key: IGNITE-3853 URL: https://issues.apache.org/jira/browse/IGNITE-3853 Project: Ignite

[jira] [Created] (IGNITE-3854) IGFS: Support direct PROXY mode invocation in method: rename

Taras Ledkov created IGNITE-3854: Summary: IGFS: Support direct PROXY mode invocation in method: rename Key: IGNITE-3854 URL: https://issues.apache.org/jira/browse/IGNITE-3854 Project: Ignite

[jira] [Created] (IGNITE-3852) IGFS: Support direct PROXY mode invocation in method: info

Taras Ledkov created IGNITE-3852: Summary: IGFS: Support direct PROXY mode invocation in method: info Key: IGNITE-3852 URL: https://issues.apache.org/jira/browse/IGNITE-3852 Project: Ignite

[jira] [Created] (IGNITE-3851) IGFS: Support direct PROXY mode invocation in method: exists

Taras Ledkov created IGNITE-3851: Summary: IGFS: Support direct PROXY mode invocation in method: exists Key: IGNITE-3851 URL: https://issues.apache.org/jira/browse/IGNITE-3851 Project: Ignite

[jira] [Created] (IGNITE-3800) IGFS: Local secondary: Add tests for local fs properties

Taras Ledkov created IGNITE-3800: Summary: IGFS: Local secondary: Add tests for local fs properties Key: IGNITE-3800 URL: https://issues.apache.org/jira/browse/IGNITE-3800 Project: Ignite

[jira] [Created] (IGNITE-3676) Fix the test IgfsDualAbstractSelfTest#testOpenNoPrefetch

Taras Ledkov created IGNITE-3676: Summary: Fix the test IgfsDualAbstractSelfTest#testOpenNoPrefetch Key: IGNITE-3676 URL: https://issues.apache.org/jira/browse/IGNITE-3676 Project: Ignite

[jira] [Created] (IGNITE-3670) IGFS: Local secondary: Add test for listPath() method called for symlink to directory

Taras Ledkov created IGNITE-3670: Summary: IGFS: Local secondary: Add test for listPath() method called for symlink to directory Key: IGNITE-3670 URL: https://issues.apache.org/jira/browse/IGNITE-3670

[jira] [Created] (IGNITE-3664) IGFS: Local secondary: Support blockSize attribute

Taras Ledkov created IGNITE-3664: Summary: IGFS: Local secondary: Support blockSize attribute Key: IGNITE-3664 URL: https://issues.apache.org/jira/browse/IGNITE-3664 Project: Ignite Issue

[jira] [Created] (IGNITE-3638) Implement rename at the LocalIgfsSecondaryFileSystem

Taras Ledkov created IGNITE-3638: Summary: Implement rename at the LocalIgfsSecondaryFileSystem Key: IGNITE-3638 URL: https://issues.apache.org/jira/browse/IGNITE-3638 Project: Ignite Issue

Re: ignite-2310

12:59, Yakov Zhdanov wrote: I replied in the ticket. --Yakov 2016-07-11 12:43 GMT+03:00 Taras Ledkov <tled...@gridgain.com>: Hi, Dmitry, thanks for your comments. I've updated the ticket with the reasons of my version of the API changes. I'm OK with the both version of the API. Ig

[jira] [Created] (IGNITE-3558) Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts

Taras Ledkov created IGNITE-3558: Summary: Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts Key: IGNITE-3558 URL: https://issues.apache.org/jira/br

Re: ignite-2310

, Jul 7, 2016 at 5:44 AM, Taras Ledkov <tled...@gridgain.com> wrote: 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

Re: ignite-2310

as well. To my knowledge, this feature ensures that a partition will not be migrated while affinityRun/Call is executed, right? On Thu, Jul 7, 2016 at 3:02 AM, Taras Ledkov <tled...@gridgain.com> wrote: Igniters, Please take a look at the next proposal of changes at IgniteCompute.affin

Re: ignite-2310

est, then why we allow it only for "affinity" methods? We can resort to "with" semantics instead: IgniteCompute.*withPartitionsToLock*(...).affinityRun(); On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov <tled...@gridgain.com> wrote: Igniters, Lets discuss the changes of

Re: ignite-2310

th" semantics instead: IgniteCompute.*withPartitionsToLock*(...).affinityRun(); On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov <tled...@gridgain.com> wrote: Igniters, Lets discuss the changes of public API at the IgniteCompute. The new methods affinityRun & affinityCall is added by wor

ignite-2310

irs of the cache name and array of partitions that must be reserved on the target node before job execution. Dmitry, colleagues, please comment or approve. -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: IgniteRDD type mapping

lain why MatchError happens? ​ -- Taras Ledkov Mail-To: tled...@gridgain.com

[jira] [Created] (IGNITE-3192) Leaks at the GridCacheQueryManager on iterator canceling

Taras Ledkov created IGNITE-3192: Summary: Leaks at the GridCacheQueryManager on iterator canceling Key: IGNITE-3192 URL: https://issues.apache.org/jira/browse/IGNITE-3192 Project: Ignite

[jira] [Created] (IGNITE-3099) Race condition on the order of events

Taras Ledkov created IGNITE-3099: Summary: Race condition on the order of events Key: IGNITE-3099 URL: https://issues.apache.org/jira/browse/IGNITE-3099 Project: Ignite Issue Type: Bug

<    1   2   3