[GitHub] ignite pull request #1604: Sorted merge index and SQL related fixes

GitHub user svladykin opened a pull request: https://github.com/apache/ignite/pull/1604 Sorted merge index and SQL related fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/svladykin/ignite ignite-1.9-midx Alternatively you

Re: IGNITE-13 (ready for review)

Hello everyone! Colleagues, take a look please at the results of measuring. Can I close this ticket ? Should I add JMH benchmark and unit test to Ignite project ? Results of measuring https://github.com/javaller/mybenchmark/blob/master/out.txt Benchmark https://github.com/javaller/mybenchmark/

Re: Continuations for services

Vladimir, This makes sense to me. Is there a ticket for separate thread pool for services? -Val On Thu, Mar 9, 2017 at 2:52 AM, Dmitriy Setrakyan wrote: > Vladimr, it sounds like what you are suggesting is allowing users specify > named executors in configuration and then use them from code, r

Re: Continuations for services

Valya, Not yet. On Thu, Mar 9, 2017 at 11:50 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vladimir, > > This makes sense to me. Is there a ticket for separate thread pool for > services? > > -Val > > On Thu, Mar 9, 2017 at 2:52 AM, Dmitriy Setrakyan > wrote: > > > Vladimr,

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

plz review ticket again вт, 28 февр. 2017 г. в 14:14, ALEKSEY KUZNETSOV : > plz review ticket again > > пн, 20 февр. 2017 г. в 11:14, Alexey Goncharuk >: > > Thanks, Aleksey, > > I will take a look this week. > > --AG > > 2017-02-20 10:25 GMT+03:00 ALEKSEY KUZNETSOV : > > > Hi! Review my PR agai

Re: Merging all network components to a single one

Dmitry, yes, your understanding is correct. Denis, I remember I already shared the idea a while ago, but completely forgot about the ticket. Thanks for bringing it up! You should give me couple of tips on how to use "Search" function in Jira :) Guys, this will be compatibility breaking change, as

[GitHub] ignite pull request #1605: Ignite 1.7.9

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

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Regarding your comment in ticket. Do you mean broken factory node ought to send notifications to cache nodes through sharedCtx.io().send(...) ? вт, 7 мар. 2017 г. в 14:23, ALEKSEY KUZNETSOV : > Regarding your comment in ticket. Do you mean broken factory node ought to > send notifications to cach

[jira] [Created] (IGNITE-4802) Create separate thread pool for services

Valentin Kulichenko created IGNITE-4802: --- Summary: Create separate thread pool for services Key: IGNITE-4802 URL: https://issues.apache.org/jira/browse/IGNITE-4802 Project: Ignite Issue

Re: Continuations for services

OK, I created it: https://issues.apache.org/jira/browse/IGNITE-4802 -Val On Thu, Mar 9, 2017 at 9:58 AM, Vladimir Ozerov wrote: > Valya, > > Not yet. > > On Thu, Mar 9, 2017 at 11:50 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Vladimir, > > > > This makes sense to me

[jira] [Created] (IGNITE-4803) Create a test to check processing doesn't break when discovery cache history overflows

Igor Seliverstov created IGNITE-4803: Summary: Create a test to check processing doesn't break when discovery cache history overflows Key: IGNITE-4803 URL: https://issues.apache.org/jira/browse/IGNITE-4803

Re: IGNITE-13 (ready for review)

Hi Vadim, Results are a bit confusing. Any idea why it's better on long string, but worse on a short string? If that's actually the case, there is no any reason to make the change and I would just close the ticket. -Val On Thu, Mar 9, 2017 at 9:20 AM, Вадим Опольский wrote: > Hello everyone! >

Re: general question

I suppose, GridDistributedCacheEntry contains common logic for Near and DHT entries, while GridDhtCacheEntry is it's subclass and contains common logic for DHT entries. For more details check the class hierarchy. On Tue, Mar 7, 2017 at 3:07 PM, ALEKSEY KUZNETSOV wrote: > I've found GridDhtCacheE

Re: general question

it looks strange. Because, DHT = distributed чт, 9 мар. 2017 г. в 14:26, Alexander Fedotov : > I suppose, GridDistributedCacheEntry contains common logic for Near and DHT > entries, while > GridDhtCacheEntry is it's subclass and contains common logic for DHT > entries. > For more details check th

[jira] [Created] (IGNITE-4804) Remove duplicated properties in parent-pom

Vyacheslav Daradur created IGNITE-4804: -- Summary: Remove duplicated properties in parent-pom Key: IGNITE-4804 URL: https://issues.apache.org/jira/browse/IGNITE-4804 Project: Ignite Issue

[jira] [Created] (IGNITE-4805) Delete GridQueryIndexType

Vladimir Ozerov created IGNITE-4805: --- Summary: Delete GridQueryIndexType Key: IGNITE-4805 URL: https://issues.apache.org/jira/browse/IGNITE-4805 Project: Ignite Issue Type: Task C

[jira] [Created] (IGNITE-4806) Infinite classLoading discovery process

Stanilovsky Evgeny created IGNITE-4806: -- Summary: Infinite classLoading discovery process Key: IGNITE-4806 URL: https://issues.apache.org/jira/browse/IGNITE-4806 Project: Ignite Issue Ty

[jira] [Created] (IGNITE-4807) Move inner classes of GridQueryProcessor to top-level if possible

Vladimir Ozerov created IGNITE-4807: --- Summary: Move inner classes of GridQueryProcessor to top-level if possible Key: IGNITE-4807 URL: https://issues.apache.org/jira/browse/IGNITE-4807 Project: Igni

[GitHub] ignite pull request #1606: IGNITE-4804

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

Re: general question

Probably, the reasoning for it is that near entries have distributed form, i.e. they are kept in sync with the changes, but actually, they aren't true DHT entries. So GridDistributedCacheEntry is the parent for GridNearCacheEntry and GridDhtCacheEntry and reflects the distributed common nature of i

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Alexey, you should understand how caches startup and partition map exchange work. I would suggest you start couple of nodes in single VM and simply do step-by-step debug in your IDE. I don't think you will need to introduce any new message, but I think you will have to add info to GridDhtPartition

Re: general question

DHT refers to server side cache. Near cache is a part of distributed cache, but not a part of DHT. -Val On Thu, Mar 9, 2017 at 3:39 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Probably, the reasoning for it is that near entries have distributed form, > i.e. they are kept in sy

[GitHub] ignite pull request #1607: IGNITE-4803

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

Re: IgniteConfiguration.gridName is very confusing

Alexander, Page https://github.com/apache/ignite/pull/1435 reports several conflicts. Can you please check and resolve if necessary. Then resubmit for review again. --Yakov 2017-03-03 13:24 GMT+03:00 Alexander Fedotov : > Hi, it's ready for review > http://reviews.ignite.apache.org/ignite/revie

Re: IgniteConfiguration.gridName is very confusing

Sure. Will take a look. On Thu, Mar 9, 2017 at 6:05 PM, Yakov Zhdanov wrote: > Alexander, > > Page https://github.com/apache/ignite/pull/1435 reports several conflicts. > Can you please check and resolve if necessary. Then resubmit for review > again. > > --Yakov > > 2017-03-03 13:24 GMT+03:00 A

general question

Hi all! Consider we've got local transaction. How can i simulate node breakage in tests so that transaction will be in ROLLED_BACK state? -- *Best Regards,* *Kuznetsov Aleksey*

general question

Hi all! Is it possible to test on multiple jvm's ? Let's say, to have multiple ignite instances deployed on different jvms ? If yes, how can i create them and address them in code ? -- *Best Regards,* *Kuznetsov Aleksey*

[jira] [Created] (IGNITE-4808) Add all Hadoop examples as Ignite unit tests with default multi-JVM execution mode

Ivan Veselovsky created IGNITE-4808: --- Summary: Add all Hadoop examples as Ignite unit tests with default multi-JVM execution mode Key: IGNITE-4808 URL: https://issues.apache.org/jira/browse/IGNITE-4808

Re: testing in multi JVM mode

Hi Aleksey, GridAbstractTest has isMultiJvm() parameter that when set to ‘true’ will execute the nodes in separate JVM processes. Refer to the tests that contain “MultiJvm” in their names as to examples of usage. P.S. Renamed the subject. Please give more specific names to email subjects. There

Re: Merging all network components to a single one

Yakov, However an end user still will be able to provide its own implementation for this combiner discovery & communication layers, right? Just want to be sure that if I want to add some custom RDMA, RoCe or InfiniBand implementation then I’ll be able to do this. — Denis > On Mar 9, 2017, at 1

Request adding to contributors list

Hi, Can someone add me to contributors list? I want to assign a ticket to myself, but unable to. Regards, Kartik

Apache Ignite SQL Grid Webinar

Igniters, Let me invite you to join the next Apache Ignite webinar that will be fully dedicated to SQL Grid component: https://www.gridgain.com/company/news/events/gridgain-webinar-apacher-ignitetm-sql-grid-hot-blend-traditional-sql-and-memory

Re: Merging all network components to a single one

To my understanding, Yakov is suggesting that we simply have one very low level SPI - let's call it IgniteTcpSpi and current implementations of discovery and communication will be removed from SPI layer and will register callbacks with this new SPI. I think this is too big of a change to try to sq

[jira] [Created] (IGNITE-4809) Cache.getAll can return partially commited results.

Andrew Mashenkov created IGNITE-4809: Summary: Cache.getAll can return partially commited results. Key: IGNITE-4809 URL: https://issues.apache.org/jira/browse/IGNITE-4809 Project: Ignite

Re: Request adding to contributors list

Hi, Kartik! What is your Apache JIRA ID? On Fri, Mar 10, 2017 at 2:38 AM, Kartik Somani < kartiksomani.offic...@gmail.com> wrote: > Hi, > > Can someone add me to contributors list? > > I want to assign a ticket to myself, but unable to. > > Regards, > Kartik > -- Alexey Kuznetsov

Re: IGNITE-2741 - spring session design

Hi Val, Did you chance to look into session handling issue ? Thanks, On Mon, Mar 6, 2017 at 3:37 PM, Rishi Yagnik wrote: > Hi Val, > > Do you think I can test a fix in 1.9 RC releases ? How are you planning to > release a fix ? > > Did you also look into problem where storing xsrf token in Ign

Re: general question

Hi Aleksey, In order to ensure that a transaction is rolled back during a node failure, you need to orchestrate messages in such a way that at least one participating node does not receive a prepare request. As an example, you can look at org.apache.ignite.internal.processors.cache.distributed.dh

Re: general question

As for the multi-jvm tests, please see isMultiJvm() method and it's overrides in GridAbstractTest. We have some basic functionality to support that kind of tests. --AG 2017-03-09 20:09 GMT+03:00 ALEKSEY KUZNETSOV : > Hi all! Is it possible to test on multiple jvm's ? Let's say, to have > multipl

Re: REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Hi! Can u plz review ticket once more вт, 7 мар. 2017 г. в 18:52, Andrey Gura : > Aleksey, thanks a lot! > > Answered in JIRA ticket. > > On Tue, Mar 7, 2017 at 1:27 PM, ALEKSEY KUZNETSOV > wrote: > > Hi! I have fixed all sources. Plz, review it again > > > > пн, 6 мар. 2017 г. в 15:43, Andrey G

Re: Request adding to contributors list

Hi Alexey, My ID is kay_jpr. Thanks & Regards, Kartik On Fri, Mar 10, 2017 at 6:33 AM, Alexey Kuznetsov wrote: > Hi, Kartik! > > What is your Apache JIRA ID? > > On Fri, Mar 10, 2017 at 2:38 AM, Kartik Somani < > kartiksomani.offic...@gmail.com> wrote: > > > Hi, > > > > Can someone add me to c

ignite-4804 - ready for review (Remove duplicated properties in parent-pom)

Hello everyone. Please review changes. https://issues.apache.org/jira/browse/IGNITE-4804 I found this mistake when I worked on an another issue. I created new issue (ignite-4804), because reviewer told me I should fix this in different task, because it didn't relates to that issue.

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

plz review ticket again чт, 9 мар. 2017 г. в 10:28, ALEKSEY KUZNETSOV : > plz review ticket again > > вт, 28 февр. 2017 г. в 14:14, ALEKSEY KUZNETSOV >: > > plz review ticket again > > пн, 20 февр. 2017 г. в 11:14, Alexey Goncharuk >: > > Thanks, Aleksey, > > I will take a look this week. > > -