Re: IgniteRDD type mapping

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

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

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

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

, 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

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: 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

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: 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

[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

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

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: 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: 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

[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: 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

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

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: Wrong SQL statement

("INSERT INTO Person VALUES(?,?)") .setArgs("Bob", 25) ); assertEquals(1L, cursor.getAll().get(0).get(0)); } } } [1] http://www.h2database.com/html/history.html [2]http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: SQL usability issues

ted. The links to the tickets are below. [1] http://dbeaver.jkiss.org/ [2] https://issues.apache.org/jira/browse/IGNITE-6048 [3] https://issues.apache.org/jira/browse/IGNITE-6046 [4] https://issues.apache.org/jira/browse/IGNITE-6047 [5] https://issues.apache.org/jira/browse/IGNITE-5233 D. -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Username/password authentication for thin clients

+ hash] [1] -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Username/password authentication for thin clients

://github.com/jeremyh/jBCrypt/blob/master/src/main/java/org/mindrot/BCrypt.java On 18.01.2018 13:50, Taras Ledkov wrote: Password hashing algorithms of the popular vendors: mysql: SHA-265, old-native-hash postgres: MD5, DES, Extended DES, Blowfish-based oracle: SHA-1 Some about "comparison"

Re: Minor version changes and server/client compatibility

to ignore the last field in the version when doing a compatibility test, e.g., 2.5.0 and 2.5.foobar would be considered compatible.Is there some reason ignite requires and exact match? How do other Ignite users handle this problem? Thanks, -DH -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Username/password authentication for thin clients

d (possibly) analysis what other vendors use. On Tue, Jan 16, 2018 at 3:56 PM, Taras Ledkov <tled...@gridgain.com> wrote: What do you think about usage bcrypt [1], [2] to store encrypted password? [1] https://stackoverflow.com/questions/1561174/sha512-vs-blowfi sh-and-bcrypt [2] https://en.wi

Re: Data compression design proposal

lopers.2346864.n4.nabble.com/Data-compression-in-Ignite-tc20679.html -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Breaking change in JDBC connection string format

ment variable. Thoughts? Vladimir. -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

; voze...@gridgain.com> wrote: Pavel, We introduced new flag IgniteConfiguration.authenticationEnabled recently. Would you mind adding it to IgniteConfigutation.cs [1]? Vladimir. [1] https://issues.apache.org/jira/browse/IGNITE-8034 -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: [IMPORTANT] Apache Ignite 2.7 and Java 11 support

9.html [5] http://www.java-countdown.xyz/ -- Taras Ledkov Mail-To: tled...@gridgain.com

Improve lazy mode SQL query execution (IGNITE-9171)

, because some data have been delivered to user and we don't track which data is delivered. PROS: - no deadlocks; - no contention on table lock for SQL query. What do you think? -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Improve lazy mode SQL query execution (IGNITE-9171)

may give them serious performance benefits (e.g. CREATE INDEX). So I propose to go with your solution for now, and start thinking about SQL -> PME integration in the background. Vladimir. On Wed, Nov 21, 2018 at 2:23 PM Taras Ledkov wrote: Hi community, We will enhance lazy mode for SQL qu

Re: Improve lazy mode SQL query execution (IGNITE-9171)

. Makes sense? On Wed, Nov 21, 2018 at 4:15 PM Taras Ledkov wrote: Vladimir, The query protocol will be changed in both solution. The tables versions must be added to the 'GridQueryNextPageResponse' message and must be compared on the reduce node too. Because the DLL / DML race may be happens

Re: SQL: INSERT with hidden columns _key, _val and check the type of input objects

t 1:52 AM Denis Magda wrote: Folks, Do we want to preserve the annotation-based configuration? There are too many ways to configure SQL indexes/fields. For instance, if our new SQL API could see and access all of the fields out-of-the-box (without any extra settings) and DDL will be used to d

Re: SQL: INSERT with hidden columns _key, _val and check the type of input objects

not into the cache. So, throw IgniteSQLException is expected behavior in this case, i think. [1]. https://issues.apache.org/jira/browse/IGNITE-5250 -- Taras Ledkov Mail-To: tled...@gridgain.com -- Taras Ledkov Mail-To: tled...@gridgain.com

SQL: INSERT with hidden columns _key, _val and check the type of input objects

onKey")' is a typical mistake of Ignite newcomers. One more argument for check: SQL INSERT sematic means the row is inserted into the specified TABLE, not into the cache. So, throw IgniteSQLException is expected behavior in this case, i think. [1]. https://issues.apache.org/jira/browse/IGNITE-5250

Re: Feature masks for thin clients

ures of thin clients on both server and client as they desire. What are your thoughts guys? Best Regards, Igor -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Feature masks for thin clients

n on these two masks. This change has many other positive effects: 1. It improves readability and also potentially simplifies debugging. 2. It gives users the ability to enable or disable features of thin clients on both server and client as they desire. What are your thoughts guys? Best Regards, Igor

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

ed partition - Fixes #7494. - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement Denis Garus, Taras Ledkov, Alexey Plekhanov, Ivan Bessonov, Can you help me with above commits and cherry-pick your contribution in ignite-2.8.1 branch? CHERRY PICKED: + d0c155fe43 IGNITE-12772 Fixed

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

ocal queries cursors must be closed or full read to unlock the GridH2Table. (#7551) - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes #7494. - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement Denis Garus, Taras Ledkov, Alexey Plekhanov, Ivan Bessonov,

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

in failure processor slow down the whole system IGNITE-12489 Error during purges by expiration: Unknown page type -- BR, Sergey Antonov -- Taras Ledkov Mail-To: tled...@gridgain.com

Introduce separate SQL configuration

may be useful to demonstrate the proposal. Please let me know your opinion. [1]. https://github.com/apache/ignite/pull/7559 -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Introduce separate SQL configuration

ged in runtime This applies to many other config properties, but we don't name them `Initial` Let's just make it SqlConfiguration. On Mon, Mar 23, 2020 at 1:04 PM Taras Ledkov wrote: Hi, Igniters. I propose to introduce separate configuration class for SQL configuration.

Command line interface to manage distributed properties

ault value. Please your comments. Please pay your attention to concept & design of the publishing a property by 'PublicProperty' and set of the new commands. [1]. https://issues.apache.org/jira/browse/IGNITE-13186 [2]. https://github.com/apache/ignite/pull/8208 -- Taras Ledkov Mail-

Re: Command line interface to manage distributed properties

x this list manually. WDYT? 3 сент. 2020 г., в 10:21, Taras Ledkov написал(а): Hi, Why do we want to restrict property management somehow? I guess some properties (may be future properties) shouldn't be published through generic cmd line interface. May be its require separate

Re: Command line interface to manage distributed properties

ers don’t have to wait «one more release» with only change ‘implements SimpleDistributedPublicProperty’ for some property. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145724615 2 сент. 2020 г., в 23:11, Taras Ledkov написал(а): Hi, Motivation: we have to manage

Re: [MTCGA]: new failures in builds [5552028] needs to be handled

-- Taras Ledkov Mail-To: tled...@gridgain.com

Re: JAR-based code deployment

drafting the IEP for this change [2]. Please let me know your thoughts. [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0#ApacheIgnite3.0-Meetups [2] https://cwiki.apache.org/confluence/display/IGNITE/IEP-59%3A+JAR-based+code+deployment -Val -- Taras Ledkov Mail-To: tled

Introduce the ability for a user to manage binary types [IGNITE-13154]

/ suggestions? [1]. https://issues.apache.org/jira/browse/IGNITE-13154 -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: Introduce the ability for a user to manage binary types [IGNITE-13154]

to solve it. The text can mention these new control.sh commands and advise to remove the old metadata. - Denis On Thu, Jun 18, 2020 at 7:42 AM Taras Ledkov wrote: Hi, I propose to introduce ability for a user to manage cluster binary types. This functionality is useful when user needs to change

Re: IGNITE-14812: Statistics

/query/stat/hll/serialization/IHLLMetadata.java -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: IGNITE-14812: Statistics

describe the features that was implemented in this merge? How users supposed to use them? Do we have plans to document? 23 июня 2021 г., в 09:21, Taras Ledkov написал(а): Hi, We have discussed BCrypt include/add dependency here [1]. AFAIK and as long as I can remember Ignite project try to minimize

Re: Questions regarding sql windows functions using apache ignite: is sql windows function supported in ignite?

your help. Bests, Xi Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 -- Taras Ledkov Mail-To: tled...@gridgain.com

[DISCUSSION] Common approach to print sensitive information

/jira/browse/IGNITE-14441 -- Taras Ledkov Mail-To: tled...@gridgain.com

[DISCUSS] Query API for Ignite 3.0

-8B5A-D2F97A82F79B -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: [DISCUSS] Query API for Ignite 3.0

and ODBC is mostly unified) вт, 6 апр. 2021 г. в 15:05, Taras Ledkov : Hi, Ignite 3.0 requires a rethinking of the query API. We have 'cache.query()' and 'SqlFieldQuery' abstractions at the Ignite 2.x native API and several JDBC implementation for clients. I propose to think about new query/SQL API

Re: [DISCUSS] IEP-71 Public API for secondary index search

exception if there is not any index that match specific criteria. BTW, Mongo DB doesn't make user to write index name in query. It just works. чт, 26 авг. 2021 г., 15:52 Taras Ledkov : Hi, It is an usability nightmare to make user write index name in all cases. I don't see any difference between

Re: [DISCUSS] IEP-71 Public API for secondary index search

dig there much. It will be a next step if this API will be implemented. I've prepared an IEP-71 for that [1] with more details. Please share your thoughts. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-71+Public+API+for+secondary+index+search -- Taras Ledkov Mail-To: tled...@gridgain.com

Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

with the suggestion - 0 - Don't care much about the suggestion - -1 - Disagree with the suggestion This is a majority vote. Voting ends in 72 hours, at 5pm PDT on October 7: https://www.timeanddate.com/counters/fullscreen.html?mode=a=20211007T17=2021=10=7=17=0=0=224 -Val -- Taras Ledkov Mail-To: tled

Re: IEP-61 Transaction API desing for Ignite 3

Hi colleagues, 2Pavel: > RecordView txView = view.withTransaction(); Can we use the syntax (see below) to attach the table / operation to the started transaction? RecordView txPersonView = person.recordView().withTransaction(txView.transaction()); On Mon, Nov 29, 2021 at 1:34 PM Pavel

[DISCUSSION] Validation key type and schema on a data insertion [IGNITE-16098]

Hi, Igniters. There was know issue described at the [IGNITE- 16098] case 1. These issue is the cause of not symmetric cache API and SQL API: we cannot create the same table by SQL and cache API (with se identical internal structures). In more detail: it is impossible now to create a sorted PK

Add ability to specify INLINE_SIZE for PK sorted index and key's schema validation [IGNITE-11402]

Hi Igniters, There is an issue to add ability to specify INLINE_SIZE for sorted index on the primary key and index on affinite fields [1]. Please take a look at the last comment (proposal). I duplicate the proposal here. *Proposal:* add to the public QueryEntity properties: - Integer

Re: [VOTE] Add micronaut dependency to Ignite 3 (reopened)

+1 On Tue, May 31, 2022 at 12:03 PM Aleksandr Pakhomov wrote: > Alexander, > > I am not sure that now we can define all > security standards that will be implemented > by Ignite 3. But I can mention the most popular: > OAuth2/OpenId, LDAP. > > I’ve mentioned them in IEP but I believe that > the

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

Dear Ignite Community! The planning release date was updated [1]: Code Freeze: September 7, 2022 Voting Date: September 21, 2022 Release Date: September 28, 2022 I delayed code freeze for two weeks because there is bunch of important patches for the release that require a bit of time to

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

: Scope Freeze: August 18, 2022 Code Freeze: August 25, 2022 Voting Date: September 8, 2022 Release Date: September 15, 2022 [1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.14 -- With best regards, Taras Ledkov

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

: Scope Freeze: August 18, 2022 Code Freeze: August 25, 2022 Voting Date: September 8, 2022 Release Date: September 15, 2022 [1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.14 PS. Fix typos at the prev message. -- With best regards, Taras Ledkov

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

Hi, 1. Petr, could you grant me TC permissions to run release builds please? 2. Pavel, please cherry pick your patch for IGNITE-17559 [1] to the release branch ignite-2.14 [2]. Or we could move the issue to the next release? [1]. https://issues.apache.org/jira/browse/IGNITE-17559 [2].

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

Dear Ignite Community! I'm announcing a code freeze for the 2.14 release [1]. Only blockers are accepted to be included to the scope. [1]. https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.14

Re:Contributor access rights

Hello! I have added you to JIRA and Wiki as contributor. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

Dear Ignite Community! Release 2.14 has been delayed due to performance issues (compare with 2.13) for IgniteSqlQueryBenchmark in in-memory mode. We're looking. Any suggestions and support are welcome.

[ANNOUNCE] Apache Ignite 2.14.0 Released

know if you encounter any problems: https://ignite.apache.org/community/resources.html#ask -- With best regards, Taras Ledkov

[VOTE] Release Apache Ignite 2.14.0 RC0

.VotingonReleaseandReleaseVerification This vote will be open for at least 3 days till Mon Oct 3, 2022, 20:00 UTC. https://www.timeanddate.com/countdown/vote?iso=20221003T20=0=VOTE+on+the+Apache+Ignite+Release+2.14.0+RC0=sanserif -- With best regards, Taras Ledkov

Re:Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

Hi, Ivan. My apologies. A blocking performance issue has been fixed [1]. And the release candidate is verified and ready to be voted on. What do you think about the 2.14.1 release, or can the fix wait until 2.15? I'm going to start VOTE just now. [1].

[RESULT] [VOTE] Release Apache Ignite 2.14.0 RC0

Pavlov (binding) - mwiesenberg 0 votes: - Ilya Kasnacheev The new release will be announced soon. -- With best regards, Taras Ledkov

Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

%27RESOLVED%27)%20ORDER%20BY%20priority -- With best regards, Taras Ledkov

Re:[DISCUSSION] Removal of ignitevisorcmd

Hi, +1 for remove Visor related code. Unfortunately we have to migrate `control-utility` to use IgniteClient (thin client) before drop GridClient. I guess we will do it in the future. Also, the old thin JDBC based on the GridClient (classes placed at the org.apache.ignite.internal.jdbc.*) must

Re:Deprecated GridSslContextFactory removal

+1 for remove

[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

[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-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

[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

[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

[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-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-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

[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-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-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-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-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-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-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

  1   2   3   >