Re: Python thin client

Dmitriy, It would be quite messy to implement with Python modular system. First of all, Python 2 and Python 3 are different languages with a small common subset of syntax rules. That's why what we see in a stack trace is a syntax error, and not a “missing feature” error. Second, there is no

[jira] [Created] (IGNITE-9467) Custom SQL function: Hexadecimal string with odd number of characters

Joe Feise created IGNITE-9467: - Summary: Custom SQL function: Hexadecimal string with odd number of characters Key: IGNITE-9467 URL: https://issues.apache.org/jira/browse/IGNITE-9467 Project: Ignite

[jira] [Created] (IGNITE-9466) AsyncFileIO may not close channel after method close invocation

Sergey Antonov created IGNITE-9466: -- Summary: AsyncFileIO may not close channel after method close invocation Key: IGNITE-9466 URL: https://issues.apache.org/jira/browse/IGNITE-9466 Project: Ignite

[GitHub] ignite pull request #4683: Ignite 2.5.1 p12 volatile

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/4683 Ignite 2.5.1 p12 volatile You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p12-volatile

[GitHub] ignite pull request #4664: IGNITE-8987 Ignite hangs during getting of atomic...

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

Re: Compression prototype

On Tue, Sep 4, 2018 at 2:55 AM, Ilya Kasnacheev wrote: > Hello! > > Each node has a local dictionary (per node currently, per cache planned). > Dictionary is never shared between nodes. As data patterns shift, > dictionary rotation is also planned. > > With Zstd, the best dictionary size seems

Possible problems with closing AsyncFileIO

Hello, Igniters! I found bug in org.apache .ignite.internal.processors.cache.persistence.file.AsyncFileIO#close(): If one of async futures (ChannelOpFuture) throw IgniteCheckedException AsynchronousFileChannel associated with AsyncFileIO instance will not be closed. It's correct behaviour or

Re: Questions about getAllInternal(...)

Hello Steve, A cache entry becomes obsolete once the on-heap object is no longer locked and is not used by any thread. Since we moved to off-heap-first model in Ignite 2.0, we must clean on-heap entries as soon as possible to keep the heap small. Thus both of the places you pointed out. Hope

[jira] [Created] (IGNITE-9463) [ML] Update ML tutorial with new model composition/update features

Aleksey Zinoviev created IGNITE-9463: Summary: [ML] Update ML tutorial with new model composition/update features Key: IGNITE-9463 URL: https://issues.apache.org/jira/browse/IGNITE-9463 Project:

[GitHub] ignite pull request #4608: IGNITE-9360 Remove SnapTreeMap and tests on it.

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

Re: Python thin client

Dmitriy, setuptools sounds like an installation step. Does it make sense to add a check during startup of a client? D. On Tue, Sep 4, 2018 at 7:25 AM, Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: > Nikolay, > > There is indeed a feature in `setuptools` I just learned about, which

Re: MVCC and transactional SQL is merged to master

Congratulations! -- Lucas BEELER Technical Consultant, Professional Services GridGain Systems, Inc. http://www.gridgain.com > On Aug 30, 2018, at 12:41 PM, Dmitriy Setrakyan wrote: > > Very nice! Looking forward to seeing this functionality in 2.7 release. > > On Thu, Aug 30, 2018 at 5:22 AM,

Re: Compression prototype

In my view, dictionary of 1024 bytes is not going to be nearly enough. On Tue, Sep 4, 2018 at 8:06 AM, Ilya Kasnacheev wrote: > Hello! > > In case of Apache Ignite, most of savings is due to BinaryObject format, > which encodes types and fields with byte sequences. Any enum/string flags > will

Re: Unknown known issue on cache rebalancing delayed

Anton, Maxim, thanks for following up! Looks like a good enough trade-off. Sorry, couldn't catch the conversation because of the different time zone ;) On Tuesday, September 4, 2018, 7:54:05 p.m. GMT+9, Anton Vinogradov wrote: Maxim, Let's create a branch with 10 checks of Sync and 10

Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source

Hi Alexey, Thank you for reviewing the changes and sharing feedback, I am updating the PR. I will share the changes shortly. Regards, Saikat On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Hello Saikat, > > I see a few fellow Igniters added some

Re: ScanQuery fails with OutOfMemory when iterating

Hi Slava, Thanks for looking into it. Looks like exactly what happened on the user side. -- Denis On Tue, Sep 4, 2018 at 5:43 AM Вячеслав Коптилин wrote: > Hi Denis, > > It looks like a known issue > https://issues.apache.org/jira/browse/IGNITE-8892 > It is already fixed and will be available

Re: Python thin client

Got it, sounds good! On Tue, Sep 4, 2018 at 10:54 AM, Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: > Dmitriy, > > It would be quite messy to implement with Python modular system. > > First of all, Python 2 and Python 3 are different languages with a small > common subset of syntax

Re: IGNITE-640: multimap initial implementation

Amir, Anton, How is dev/review process going? Is there any chance we get this capability into 2.7? -- Denis On Mon, Jul 9, 2018 at 10:27 PM Amir Akhmedov wrote: > Hi Anton, > > I checked your last comments in the ticket and left some responses. Please > check them and let me know > > Thanks,

Re: Hi... trying to write a test case for a pacth ... need help....

Hi Paul, what Jira ticket are you working on? On Tue, Sep 4, 2018 at 7:02 AM, Paul Anderson wrote: > ... The code is done ready to go, but the test suite looks huge, I know the > two test classes I have to augment... but I am unsure of a couple of > things. > > 1) how do I run a specific test

[GitHub] ignite pull request #4592: IGNITE-9054 Avoid using OptimizedMarshaller with ...

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

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214728863 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/issues/IssueRef.java ##

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214727827 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214726814 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/RelatedIssuesRef.java ##

[GitHub] ignite pull request #4671: Ignite 9448

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

[GitHub] ignite pull request #4659: IGNITE-9387: update interface for trainers

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

[jira] [Created] (IGNITE-9465) Node.js client: improve complex object flags processing

Alexey Kosenchuk created IGNITE-9465: Summary: Node.js client: improve complex object flags processing Key: IGNITE-9465 URL: https://issues.apache.org/jira/browse/IGNITE-9465 Project: Ignite

Re: Table Names in Spark Catalog

Hello, Stuart. Sorry for the silence. I was swamped the last couple of days. I think you can go forward and implement suggested solution. I'm -0 with it. So no block from my side, but I'm still no happy with abstractions :). В Пн, 03/09/2018 в 09:35 +0100, Stuart Macdonald пишет: > Nikolay,

[jira] [Created] (IGNITE-9464) MVCC TX: cache GET supports Mvcc tx mode.

Andrew Mashenkov created IGNITE-9464: Summary: MVCC TX: cache GET supports Mvcc tx mode. Key: IGNITE-9464 URL: https://issues.apache.org/jira/browse/IGNITE-9464 Project: Ignite Issue

Hi... trying to write a test case for a pacth ... need help....

... The code is done ready to go, but the test suite looks huge, I know the two test classes I have to augment... but I am unsure of a couple of things. 1) how do I run a specific test (command line) 2) how do I start (make sure is started) an ignite instance

[GitHub] ignite pull request #4592: IGNITE-9054 Avoid using OptimizedMarshaller with ...

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

[jira] [Created] (IGNITE-9462) ADD originator to EVT_NODE_LEFT

Yuriy Sergeev created IGNITE-9462: - Summary: ADD originator to EVT_NODE_LEFT Key: IGNITE-9462 URL: https://issues.apache.org/jira/browse/IGNITE-9462 Project: Ignite Issue Type: Task

Re: Possible problems with closing AsyncFileIO

Hello, Sergey. If some resources are not closed after usage it certainly a bug. Can you create a ticket and attach a simplest reproducer for desribed issue? В Вт, 04/09/2018 в 17:44 +0300, Sergey Antonov пишет: > Hello, Igniters! > > I found bug in org.apache >

[GitHub] ignite pull request #4682: IGNITE-6454 muted flaky tests

GitHub user dgarus opened a pull request: https://github.com/apache/ignite/pull/4682 IGNITE-6454 muted flaky tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/dgarus/ignite IGNITE-6454 Alternatively you can review and apply

Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source

Hello Saikat, I see a few fellow Igniters added some comments to your PR (including me). I believe the PR can be merged after you address them. Thanks, AG пт, 31 авг. 2018 г. в 3:11, Saikat Maitra : > Thank you, Denis > > Regards, > Saikat > > On Thu, Aug 30, 2018 at 7:01 PM, Denis Magda

[GitHub] ignite pull request #4681: IGNITE-9422 Fixed NPE on clients when new binary ...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/4681 IGNITE-9422 Fixed NPE on clients when new binary meta from joined nod… …e arrived. You can merge this pull request into a Git repository by running: $ git pull

Re: Compression prototype

Hello! In case of Apache Ignite, most of savings is due to BinaryObject format, which encodes types and fields with byte sequences. Any enum/string flags will also get in dictionary. And then as it processes a record it fills up its individual dictionary. But, in one cache, most if not all

[GitHub] ignite pull request #4592: IGNITE-9054 Avoid using OptimizedMarshaller with ...

GitHub user alamar reopened a pull request: https://github.com/apache/ignite/pull/4592 IGNITE-9054 Avoid using OptimizedMarshaller with initial ScanQuery. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Python thin client

Nikolay, There is indeed a feature in `setuptools` I just learned about, which would help in this case (and I believe the case you demonstrated can be quite typical, thank you for pointing it out). It gives user a clever message in the end of a stack trace like > UnsupportedPythonVersion:

Re: Failed to activate node components

POC5-server.xml Here is my config file -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Failed to activate node components

this is how i am starting the service - IgniteConfiguration cfg = Ignition.loadSpringBean("POC5-server.xml","grid.cfg"); Ignite ig =Ignition.start(cfg); ig.cluster().active(true); *i should point out that if i start it like this i don't get the error* Ignite ig =

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214729838 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214714321 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java ## @@

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214725893 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java ## @@

[GitHub] akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page

akalash commented on a change in pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214726174 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java ## @@

[GitHub] ignite pull request #4680: IGNITE-9442

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4680 IGNITE-9442 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-9442 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #4583: IGNITE-8829

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

Re: PHP thin client

Great, I'll take a look Best Regards, Igor On Wed, Aug 29, 2018 at 10:37 PM Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: > Hi folks, > > PHP thin client is ready for review. > > Jira with the scope of work - [1]. > > Implementation, examples, tests: >PR - [2], >repository

Re: ScanQuery fails with OutOfMemory when iterating

Hi Denis, It looks like a known issue https://issues.apache.org/jira/browse/IGNITE-8892 It is already fixed and will be available in Apache Ignite 2.7 Thanks, S. вс, 2 сент. 2018 г. в 17:40, Denis Magda : > Igniters, > > A user reported the issue on SO: > >

[GitHub] ignite pull request #4666: Ignite 1.8.20

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

Re: Unknown known issue on cache rebalancing delayed

Maxim, Let's create a branch with 10 checks of Sync and 10 checks of Async. Then, run it 20 times at TC. This should be enough I think. вт, 4 сент. 2018 г. в 13:09, Maxim Muzafarov : > Anton, > > I agree with you 20 time is not enough. I've checked the single run of the > test class - it

[jira] [Created] (IGNITE-9461) Implement random subspace method and provide an option to combine it with bagging

Oleg Ignatenko created IGNITE-9461: -- Summary: Implement random subspace method and provide an option to combine it with bagging Key: IGNITE-9461 URL: https://issues.apache.org/jira/browse/IGNITE-9461

[GitHub] ignite pull request #4679: IGNITE-8927

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

[GitHub] ignite pull request #4678: IGNITE-9361 Remove IgniteInternalCache.isMongo*Ca...

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

[jira] [Created] (IGNITE-9460) Update styles on WC top menu

Alexander Kalinin created IGNITE-9460: - Summary: Update styles on WC top menu Key: IGNITE-9460 URL: https://issues.apache.org/jira/browse/IGNITE-9460 Project: Ignite Issue Type: Bug

Re: Apache Ignite 2.7 release

Thanks, Ilya!I will check your comments, and discuss it at JIRA. -- Roman Shtykh On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev wrote: Hello! IGNITE-9408 looks good to me and may be merged right away. IGNITE-9388 needs more work in my opinion, I have commented the

Re: Workflow improvement

Hi Dmitrii, Great news. I love the fact that you did these improvements. I have limited access to the internet so for now I'm not able to review and merge. I can do it next week. I appreciate your effort. Sincerely, Dmitriy Pavlov пн, 3 сент. 2018 г., 18:20 Dmitrii Ryabov : > Hi, Dmitriy, >

Re: Hello!

Hello Ivan, Welcome to the Ignite community! I've added you to the list of contributors, you should now be able to assign tickets to yourself. Get familiar with Apache Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions

Re: Compression prototype

Hello! The compression is per-binary-object, but dictionary is external, shared between multiple (millions of) entries and stored alongside compressed data. Regards, -- Ilya Kasnacheev вт, 4 сент. 2018 г. в 2:40, Dmitriy Setrakyan : > Hi Ilya, > > This is very useful. Is the compression

Re: Compression prototype

On Tue, Sep 4, 2018 at 1:16 AM, Ilya Kasnacheev wrote: > Hello! > > The compression is per-binary-object, but dictionary is external, shared > between multiple (millions of) entries and stored alongside compressed > data. > I was under a different impression. If the dictionary is for the whole

[GitHub] SomeFire opened a new pull request #5: IGNITE-9377

SomeFire opened a new pull request #5: IGNITE-9377 URL: https://github.com/apache/ignite-teamcity-bot/pull/5 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

Relevance of savepoints support inside of Ignite Transactions

Hi, Igniters! I have an implementation for savepoints support inside of transactions, which was reviewed by Boikov a year ago. It allows us to rollback piece of the transaction, not whole tx. Current restrictions: * Doesn't work with near caches. * MVCC should be disabled. MVCC was merged

[jira] [Created] (IGNITE-9459) MVCC Cache.size corner cases

Ivan Pavlukhin created IGNITE-9459: -- Summary: MVCC Cache.size corner cases Key: IGNITE-9459 URL: https://issues.apache.org/jira/browse/IGNITE-9459 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #4652: IGNITE-9433 Extracted zip suffix constant

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

Re: Unknown known issue on cache rebalancing delayed

Anton, Thank you. I would like to recheck it. How can this (1_000 runs) be done in TC? On Tuesday, September 4, 2018, 5:42:01 p.m. GMT+9, Anton Vinogradov wrote: Roman, I see you uncommented this line. I do not remember deadlock detail, but I remember it was the extremely rare case.

Re: Unknown known issue on cache rebalancing delayed

Anton, I agree with you 20 time is not enough. I've checked the single run of the test class - it consumes ~7min per each execution. CacheSuite8 total execution timeout - 210 min, so we can perform only 30 class execution in this suite. Our strategy here is to `20 times within single` and put

Re: Unknown known issue on cache rebalancing delayed

Roman, I see you uncommented this line. I do not remember deadlock detail, but I remember it was the extremely rare case. I found and "fixed" it some days before merge when I had 24x7 sanity check week :) So, I propose to have at least 1_000 runs of this tests before keeping this uncommented.

Questions about getAllInternal(...)

Hello, in the case of local caches without eviction policy. I have the following questions: 1) I would to understand why, in the method, getAllInternal the method entryEx(cacheKey); uses the topology in the case of a local cache. Furthermore, it calls the method map.putEntryIfObsoleteOrAbsent.

Re: Unknown known issue on cache rebalancing delayed

Roman, Anton, I've already created additional PR [2] all and run it on TC [1]. Please, follow up with the results. [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache8=buildTypeStatusDiv_IgniteTests24Java8=pull%2F4676%2Fhead [2]

Re: Unknown known issue on cache rebalancing delayed

Maxim, 20 is not 1k :) Also, you forgot to check GridCacheRebalancingAsyncSelfTest I'm not sure we should have exactly 1k runs, but 20 is definitely not enough. Roman, I propose to use IDEA "run until failure" feature and perform test locally (at your PC) while you're not using PC. вт, 4 сент.

[GitHub] ignite pull request #4536: IGNITE-9141 Implemented

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

Re: Python thin client

Hello, Dmitry. I understand that for experienced Python developer it obvious from stack trace I send. But can we check python version on startup? And print big fat error message "You are using wrong python version". From my experience, there are some tickets in Ignite that should be

[GitHub] ignite pull request #4676: Run 20 times rebalancing sync test

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/4676 Run 20 times rebalancing sync test You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ig-9353-long Alternatively you can review and

[GitHub] ignite pull request #4677: Ignite 6195

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

Re: Compression prototype

Hello! Each node has a local dictionary (per node currently, per cache planned). Dictionary is never shared between nodes. As data patterns shift, dictionary rotation is also planned. With Zstd, the best dictionary size seems to be 1024 bytes. I imagine It is enough to store common BinaryObject

Re: Apache Ignite 2.7 release

Hello! IGNITE-9408 looks good to me and may be merged right away. IGNITE-9388 needs more work in my opinion, I have commented the PR. I also advice having test for this functionality.

[GitHub] ignite pull request #4678: IGNITE-9361 Remove IgniteInternalCache.isMongo*Ca...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4678 IGNITE-9361 Remove IgniteInternalCache.isMongo*Cache() and other remn… …ants. You can merge this pull request into a Git repository by running: $ git pull