Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

out. > > As far as configuration, we can do it as follows: > > 1) Add global encoding, UTF8 by default. > 2) Add per-cache encoding. > 3) Add encoding to JDBC and ODBC driver properties. > > This should be enough. > > -- Best regards, Andrey Kuznetsov. -- View this messa

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

Currently, marshaller determines the type of field (BYTE, INT, STRING etc.) only by the Class of data being serialized. It seems rather non-trivial to manage marshaling parameters at cache creation point. Alternatively, there exists simple and flexible way: just to introduce new Java type, say,

[GitHub] ignite pull request #2391: Ignite 5655

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2391 Ignite 5655 First implementation, uses global level configuration option (in BinaryConfiguration) You can merge this pull request into a Git repository by running: $ git pull https

IgniteSemaphore methods semantics

ion, while java.util.concurrent.Semaphore is bounded. I think we are to do one of the following: - Document uncommon IgniteSemaphore semantics properly or - Change its semantics to conform java.util.concurrent counterpart. -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #2434: IGNITE-6009: Fixed IgniteSemaphore test.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2434 IGNITE-6009: Fixed IgniteSemaphore test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6009

Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

operty. It seems to be more convenient for user.I'll appreciate your feedback. - Best regards, Andrey Kuznetsov. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Non-UTF-8-string-encoding-support-in-BinaryMarshaller-IGNITE-5655-tp20024.html Sent from the

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

property for encoding to use instead of using global property. It seems to be more convenient for user. I'll appreciate your feedback. 2017-07-25 16:13 GMT+03:00 Andrey Kuznetsov <stku...@gmail.com>: > Hi Igniters,I'd like to discuss future changes related to IGNITE-5655

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

cial value, meaning that encoding will be written as string > afterwards, this way we will support any encoding out of the box > [optional] encoding name > 4 bytes - string length > Finally - string bytes > > Vladimir. > > вт, 25 июля 2017 г. в 18:24, Andrey Kuznetsov <[hidden e

Assertions as binary data validation checks in deserialization

. -- Best regards, Andrey Kuznetsov.

Re: Assertions as binary data validation checks in deserialization

писал: > Andrey, > > How will it corrupt the data? Assertions only reads the array, not updates > it, right? > > -Val > > On Thu, Jul 27, 2017 at 8:54 AM, Andrey Kuznetsov <stku...@gmail.com> > wrote: > > > Hi Igniters, > > > > While

Re: Assertions as binary data validation checks in deserialization

May I change this line while working on existing ticket, unless someone else objects? 27 июля 2017 г. 23:37 пользователь "Valentin Kulichenko" < valentin.kuliche...@gmail.com> написал: Makes sense to me. Feel free to create a ticket unless someone else has any objection. However, I think that we

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

1 byte - type > > > 1 byte - encoding code, map frequently used encodings to some byte > value; > > > also have a special value, meaning that encoding will be written as > > string > > > afterwards, this way we will support any encoding out of the box > > >

[GitHub] ignite pull request #2339: Ignite 4181 public api

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2339 Ignite 4181 public api You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-4181-public-api Alternatively

Re: Ignite Enhancement Proposal process

ZNETSOV <alkuznetsov...@gmail.com>: > great suggestion > > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #2869: IGNITE-1804: Test is not not flaky anymore

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2869 IGNITE-1804: Test is not not flaky anymore You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite master

IGNITE-5655: Mixing binary string encodings in Ignite cluster

goes down for a while. Any ideas on addressing these issues? -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #2749: IGNITE-6186: Removed redundant parameter.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2749 IGNITE-6186: Removed redundant parameter. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6186

[GitHub] ignite pull request #2781: IGNITE-6520: Using actual AffinityReadyFuture res...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2781 ---

[GitHub] ignite pull request #2781: IGNITE-6520: Using actual AffinityReadyFuture res...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2781 IGNITE-6520: Using actual AffinityReadyFuture result. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite

[GitHub] ignite pull request #2748: IGNITE-6015: Rollback on exception in commitIfLoc...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2748 IGNITE-6015: Rollback on exception in commitIfLocked. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite

Re: Ignite Usability: Deadlocks and Starvation

+03:00 Yakov Zhdanov <yzhda...@apache.org>: > Andrey, do you have an example of such method in Ignite public or private > API? > > If it is not Ignite API please provide an example. > > -- > Yakov Zhdanov > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #2496: IGNITE-6137: CAS logic fix in async commit.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2496 IGNITE-6137: CAS logic fix in async commit. Reproducing test + fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov

Re: Ignite Usability: Deadlocks and Starvation

thread as parameter. > > --Yakov > -- Best regards, Andrey Kuznetsov.

Re: Ignite Usability: Deadlocks and Starvation

to plan these changes. > > --Yakov > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #2877: IGNITE-1804: Test is not flaky anymore

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/2877 IGNITE-1804: Test is not flaky anymore You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-1804

[GitHub] ignite pull request #2869: IGNITE-1804: Test is not flaky anymore

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2869 ---

[GitHub] ignite pull request #3072: IGNITE-6963: Made PhysicalMemoryPages equal to To...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3072 ---

[GitHub] ignite pull request #3232: IGNITE-6731: Dropping unnecessary PerfCounter inv...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3232 IGNITE-6731: Dropping unnecessary PerfCounter invocations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

Switching Java language level to 8

://issues.apache.org/jira/browse/IGNITE-6734 -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #3248: IGNITE-6736: Switched GridCacheMapEntry synchroni...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3248 IGNITE-6736: Switched GridCacheMapEntry synchronization to locks. For test purpose You can merge this pull request into a Git repository by running: $ git pull https://github.com

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

lict. > > https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_ > IgniteStartNodes=buildTypeHistoryList_ > Ignite20Tests=%3Cdefault%3E > > > -- Best regards, Andrey Kuznetsov.

Separate code paths for Java 8 and Java 9

utility classes. Could someone share the ideas on the content of potential version-specific modules? [1] https://issues.apache.org/jira/browse/IGNITE-6730 [2] https://issues.apache.org/jira/browse/IGNITE-6728 -- Best regards, Andrey Kuznetsov.

Re: Time and scope for Apache Ignite 2.4

t; - Nikolay Izhikov: Data Frames. > - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list. > - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks. > - Yuri: Machine Learning + neural networks > - Vladimir Ozerov: Java 9 and Java 7 > - Sergey Kozlov: SQL sco

Add emergency node closing handler to public Ignite API

). First, I'd like to get your feedback on this potential change. Then we can refine SomeClosure structure. -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #3072: IGNITE-6963: Made PhysicalMemoryPages equal to To...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3072 IGNITE-6963: Made PhysicalMemoryPages equal to TotalAllocatedPages when PDS is off You can merge this pull request into a Git repository by running: $ git pull https://github.com

Re: Add emergency node closing handler to public Ignite API

Vladimir, Could you please refine, what are local metrics? Should I extend Ignite interface by adding something similar to dataRegionMetrics() or there is some universal mechanism to handle metrics? 2017-11-15 8:30 GMT+03:00 Vladimir Ozerov : > > This information should be

Re: Add emergency node closing handler to public Ignite API

Vladimir, Ignite instance won't tell me whether deadlock occurred or some critical thread has died. 14 нояб. 2017 г. 22:28 пользователь "Vladimir Ozerov" написал: You can get this info from injected Ignite instance.

Re: Add emergency node closing handler to public Ignite API

Lifecycle beans are ok, but they does not accept any info on the Reason in case of emergency node stop. 2017-11-14 21:16 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Anton, > > I agree with Vova - we already have lifecycle bean. Why do we need anything > on top of that? > >

[GitHub] ignite pull request #3181: Ignite 6902

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3181 Ignite 6902 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6902 Alternatively you can review

[GitHub] ignite pull request #3184: IGNITE-6729: Removed obsolete reflection-based wo...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3184 IGNITE-6729: Removed obsolete reflection-based workaround You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

[GitHub] ignite pull request #3165: IGNITE-6711: TotalAllocatedPages metric fix.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3165 IGNITE-6711: TotalAllocatedPages metric fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6711

[GitHub] ignite pull request #2877: IGNITE-1804: Test is not flaky anymore

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2877 ---

[GitHub] ignite pull request #3197: Ignite 6734

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3197 Ignite 6734 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6734 Alternatively you can review

[GitHub] ignite pull request #2434: IGNITE-6009: Fixed IgniteSemaphore test.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2434 ---

[GitHub] ignite pull request #3199: IGNITE-6740: Replaced direct sun.nio.ch.DirectBuf...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3199 IGNITE-6740: Replaced direct sun.nio.ch.DirectBuffer.address() call with reflective one You can merge this pull request into a Git repository by running: $ git pull https

IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

Hi Igniters, IgniteProjectionStartStopRestartSelfTest fails with timeout on TeamCity, maybe due to some infrastructure issues. Can anybody take a look? -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #3206: IGNITE-6743: Cleaning direct buffer through refle...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3206 IGNITE-6743: Cleaning direct buffer through reflection. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

IgniteSet implementation: changes required

Hi, Igniters! Current implementation of IgniteSet is fragile with respect to cluster recovery from a checkpoint. We have an issue (IGNITE-5553) that addresses set's size() behavior, but the problem is slightly broader. The text below is my comment from Jira issue. I encourage you to discuss it.

Re: Transaction classes naming

t; > How about: > OriginatingTx for transaction created on originating node > PrimaryTx for transaction created on primary nodes, but not the originating > node > BackupTx for transaction created on backup nodes > NearTx for transaction created to update near cache > > Thoughts? > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #3269: IGNITE-6732: Preventing Hadoop module from start ...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3269 IGNITE-6732: Preventing Hadoop module from start on Java >= 9. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznet

Re: Ticket review checklist

original error. > All exceptions thrown to a user *SHOULD* have explanation how to resolve if > possible. > ? > > вт, 8 мая 2018 г. в 12:26, Andrey Kuznetsov <stku...@gmail.com>: > > > Vladimir, checklist looks pleasant enough for me. > > > > I'd like to s

Re: Ticket review checklist

t; > Don't fix if it works! > > > > >> > > > > > >> > If you 100% sure then it a useful addition to the product - just > > > make > > > > a > > > > >> > separate ticket. > > > > >> >

[GitHub] ignite pull request #4015: Ignite 6587

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4015 Ignite 6587 For test purposes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6587 Alternatively you

Re: Avoid JIRA comments deletion

-05-16 12:51 GMT+03:00 Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com> : > +1 Dmitriy, > > I do not see any reason for deletion comments. > Maybe only edit operation must be allowed. > > -- Best regards, Andrey Kuznetsov.

Re: supporting different configuration format json,yaml...

;> > > > > > > > > > >> > > вт, 15 мая 2018 г. в 9:31, Pavel Tupitsyn < > > > > ptupit...@apache.org > > > > > >: > > > > > > > >> > > > > > > > > > >> > > > Dmitriy, > > > > > > > >> > > > > > > > > > > >> > > > We don't need to support different config formats on > > > server > > > > in > > > > > > > order > > > > > > > >> to > > > > > > > >> > > add > > > > > > > >> > > > that to thin clients. > > > > > > > >> > > > > > > > > > > >> > > > Thin client protocol provides a way to create a cache > > with > > > > > > custom > > > > > > > >> > config > > > > > > > >> > > > [1]. > > > > > > > >> > > > It is up to thin client library authors to use any > > config > > > > > format > > > > > > > they > > > > > > > >> > > like > > > > > > > >> > > > and then convert it into protocol-defined format. > > > > > > > >> > > > > > > > > > > >> > > > C# thin client uses custom format, for example, not > > > Spring. > > > > > > > >> > > > > > > > > > > >> > > > [1] > > > > > > > >> > > > > > > > > > > >> > > > https://apacheignite.readme.io/docs/binary-client- > > > > > > > >> > > protocol-cache-configuration- > operations#section-op_cache_ > > > > > > > >> > > create_with_configuration > > > > > > > >> > > > > > > > > > > >> > > > On Mon, May 14, 2018 at 7:54 PM, Ivan Rakov < > > > > > > > ivan.glu...@gmail.com> > > > > > > > >> > > wrote: > > > > > > > >> > > > > > > > > > > >> > > > > Dmitry, > > > > > > > >> > > > > > > > > > > > >> > > > > We rely on Spring Framework when we start Ignite > node > > > from > > > > > XML > > > > > > > >> > > > > configuration. Spring doesn't easily support another > > > > formats > > > > > > of > > > > > > > >> > > > > configuration files. I think, the main reason for > this > > > is > > > > > > > built-in > > > > > > > >> > > > ability > > > > > > > >> > > > > to validate configuration via XML Schema. We can > > surely > > > > hack > > > > > > > this > > > > > > > >> > > around > > > > > > > >> > > > (I > > > > > > > >> > > > > bet there are existing libraries for configuring > > Spring > > > > with > > > > > > > JSON), > > > > > > > >> > > but I > > > > > > > >> > > > > don't think that anyone suffered from inability to > > > > > statically > > > > > > > >> > configure > > > > > > > >> > > > > Ignite with json/yaml. > > > > > > > >> > > > > > > > > > > > >> > > > > Regarding thin clients: makes sense. I suppose > > necessary > > > > > > > mappings > > > > > > > >> > will > > > > > > > >> > > be > > > > > > > >> > > > > implemented as a part of thin client. > > > > > > > >> > > > > > > > > > > > >> > > > > Best Regards, > > > > > > > >> > > > > Ivan Rakov > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > On 14.05.2018 18:58, Dmitriy Govorukhin wrote: > > > > > > > >> > > > > > > > > > > > >> > > > >> Hi, Igniters! > > > > > > > >> > > > >> > > > > > > > >> > > > >> As far as I know, many people work on a thin client > > for > > > > > > > different > > > > > > > >> > > > language > > > > > > > >> > > > >> (go,js,php...). > > > > > > > >> > > > >> Are there any reasons why ignite does not support > > yaml > > > or > > > > > > json > > > > > > > >> > format > > > > > > > >> > > > for > > > > > > > >> > > > >> configuration? or some other popular format? > > > > > > > >> > > > >> In future, it can help to integrate with thin > > clients, > > > > for > > > > > > > >> example, > > > > > > > >> > js > > > > > > > >> > > > >> client may want to dynamic cache start, he passes > > cache > > > > > > > >> > configuration > > > > > > > >> > > > (in > > > > > > > >> > > > >> native format, for js it will json) through TCP, > > Ignite > > > > > node > > > > > > > >> unwrap > > > > > > > >> > > and > > > > > > > >> > > > >> remap to java representation and dynamic start > cache. > > > > > > > >> > > > >> > > > > > > > >> > > > >> > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best regards, Andrey Kuznetsov.

Unreliable checks in tests for string presence in GridStringLogger contents

that add more logging can damage a test. I propose to add some stuff to {{GridStringLogger}} in order to catch preset marker strings during logging, then we will not depend on buffer size. Thoughts? -- Best regards, Andrey Kuznetsov.

Re: Unreliable checks in tests for string presence in GridStringLogger contents

ework/ > junits/logger/ListenedGridTestLog4jLogger.java > [2] https://github.com/apache/ignite/blob/master/modules/ > compatibility/src/test/java/org/apache/ignite/compatibility/testframework/ > junits/IgniteCompatibilityAbstractTest.java#L304 > > > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #4091: IGNITE-8642: Added thread dumping to FailureProce...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4091 ---

[GitHub] ignite pull request #4173: IGNITE-8562: As single large commit.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4173 IGNITE-8562: As single large commit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-8562-2

[GitHub] ignite pull request #4121: IGNITE-8562: Squashed partial commits.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4121 ---

[GitHub] ignite pull request #3861: IGNITE-8303: Avoided failure handler invocation w...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3861 ---

[GitHub] ignite pull request #3652: IGNITE-7770 A bunch of changes to fix tx timeout ...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3652 ---

[GitHub] ignite pull request #3843: Ignite 7770 2

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3843 ---

[GitHub] ignite pull request #3870: IGNITE-8312: Simplified the choice of exception t...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3870 ---

[GitHub] ignite pull request #4173: IGNITE-8562: As single large commit.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4173 ---

[GitHub] ignite pull request #4091: IGNITE-8642: Added thread dumping to FailureProce...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4091 IGNITE-8642: Added thread dumping to FailureProcessor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite

[GitHub] ignite pull request #4115: IGNITE-8290: Trying to reproduce on TC.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4115 IGNITE-8290: Trying to reproduce on TC. Debug through CI. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

[GitHub] ignite pull request #4121: IGNITE-8562: Squashed partial commits.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4121 IGNITE-8562: Squashed partial commits. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-8562

[GitHub] ignite pull request #4089: Ignite 6587 true

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4089 Ignite 6587 true For TC tests now You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6587-true

[GitHub] ignite pull request #4266: IGNITE-8885 Failing test method explicitly.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4266 IGNITE-8885 Failing test method explicitly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-8885

[GitHub] ignite pull request #4265: IGNITE-8887 Failing test method explicitly.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4265 IGNITE-8887 Failing test method explicitly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-8887

[GitHub] ignite pull request #3302: IGNITE-7312: Made use of java.util.Base64 for bas...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3302 IGNITE-7312: Made use of java.util.Base64 for base64 encoding. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov

Re: Java 9 support

anges into ignite-6730 to have working compiling > under Java 9 branch — so that we can continue work on improving Apache > Ignite’s Java 9 support. -- Best regards, Andrey Kuznetsov.

Re: Java 9 support

736 to become > subtasks in the process). > What do you think? > > > > On 9 Jan 2018, at 20:49, Andrey Kuznetsov <stku...@gmail.com> wrote: > > > > Hi Petr! > > > > Could you please clarify what is wrong with fix proposed in IGNITE-6736, > > and what is suppo

Re: Java 9 support

No. We got rid of monitorEnter/monitorExit there. And ReentrantLock is supposed to be a replacement. 2018-01-10 13:49 GMT+03:00 Антон Чураев <churaev...@gmail.com>: > Andrey, do You mean https://issues.apache.org/jira/browse/IGNITE-4908? > > > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #3377: IGNITE-7386: Got rid of ThreadLocalRandom8.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3377 IGNITE-7386: Got rid of ThreadLocalRandom8. For test purposes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

[GitHub] ignite pull request #3181: Ignite 6902

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3181 ---

Eliminating org.jsr166 from Ignite codebase

] https://issues.apache.org/jira/browse/IGNITE-7516 [4] https://issues.apache.org/jira/browse/IGNITE-7517 -- Best regards, Andrey Kuznetsov.

Re: IgniteSet implementation: changes required

Hi all, Current set implementation has significant flaw: all set data are duplicated in onheap maps on _every_ node in order to make iterator() and size(). For me it looks like simple yet ineffective implementation. Currently, these maps are damaged by checkpointing/recovery, and we could patch

Re: IgniteSet implementation: changes required

Indeed, all sets, regardless of whether they collocated or not, share single cache, and also use onheap data structures irresistable to checkpointing/recovery. 2018-02-13 2:14 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > On Fri, Feb 9, 2018 at 6:26 PM, Andrey Kuznet

[GitHub] ignite pull request #3525: Ignite 7517

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3525 Ignite 7517 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-7517 Alternatively you can review

EvictableEntry.isCached() state meaning

t is, if I call getKey() or getValue() on removed entry it will be resurrected in cache? This sounds too magically. Could someone explain the real message of the phrase, please? -- Best regards, Andrey Kuznetsov.

Re: Stop nodes after test by default - IGNITE-6842

; IgniteBaselineAffinityTopologyActivationTest#afterTest > we call method stopAllGrids(false) this way. Why not "true" argument > instead? > > > -- Best regards, Andrey Kuznetsov.

Re: Abandoned Patch Available JIRA tickets

committers. > > Not sure I like the latter approach and would rather go for the one when > both the committers and contributors are proactive and disciplined. But > guess what, if you want to make the contributors proactive then the > committers have to be an example. > > — > Denis > > > -- Best regards, Andrey Kuznetsov.

[GitHub] ignite pull request #3165: IGNITE-6711: TotalAllocatedPages metric fix.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3165 ---

[GitHub] ignite pull request #3428: Ignite 7513

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3428 ---

[GitHub] ignite pull request #3377: IGNITE-7386: Got rid of ThreadLocalRandom8.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3377 ---

[GitHub] ignite pull request #2339: Ignite 4181 public api

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2339 ---

[GitHub] ignite pull request #3197: Ignite 6734

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3197 ---

[GitHub] ignite pull request #3248: IGNITE-6736: Switched GridCacheMapEntry synchroni...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3248 ---

[GitHub] ignite pull request #3302: IGNITE-7312: Made use of java.util.Base64 for bas...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3302 ---

[GitHub] ignite pull request #3531: IGNITE-7685: Fixed allocation rate.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3531 IGNITE-7685: Fixed allocation rate. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-7685

[GitHub] ignite pull request #3197: Ignite 6734

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3197 ---

[GitHub] ignite pull request #3206: IGNITE-6743: Cleaning direct buffer through refle...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3206 ---

[GitHub] ignite pull request #3197: Ignite 6734

GitHub user andrey-kuznetsov reopened a pull request: https://github.com/apache/ignite/pull/3197 Ignite 6734 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6734 Alternatively you can review

[GitHub] ignite pull request #2748: IGNITE-6015: Rollback on exception in commitIfLoc...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2748 ---

Re: Time and scope for Apache Ignite 2.4

working on Java 9 specific tasks: > https://issues.apache.org/jira/browse/IGNITE-6728 < > https://issues.apache.org/jira/browse/IGNITE-6728> > > Is everything alright there? If you need a review try to ping a reviewer > directly. > > — > Denis > > > On Dec 20, 201

[GitHub] ignite pull request #3199: IGNITE-6740: Replaced direct sun.nio.ch.DirectBuf...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3199 ---

[GitHub] ignite pull request #3184: IGNITE-6729: Removed obsolete reflection-based wo...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3184 ---

Re: IEP-22: Direct Data Load proposal

s one the first things user try to do with Ignite. And if it takes > too much time, it is very likely that user will look for other solutions. > Best regards, Andrey Kuznetsov.

  1   2   3   >