[jira] [Created] (IGNITE-4928) .NET: Add DML to LINQPad examples

Pavel Tupitsyn created IGNITE-4928: -- Summary: .NET: Add DML to LINQPad examples Key: IGNITE-4928 URL: https://issues.apache.org/jira/browse/IGNITE-4928 Project: Ignite Issue Type:

Re: Stable binary key representation

Dima, Yes, they may explode some internals of our indexes. 06 апр. 2017 г. 23:32 пользователь "Dmitriy Setrakyan" < dsetrak...@apache.org> написал: > Guys, > > Isn't the main issue here that we cannot use the Identity Resolvers in > BTrees in the 2.0 version? If yes, then we have to remove them

Re: IGNITE-4809

Alexey K, sorry for being pedantic but let my share the same suggestion I shared with Vadim yesterday: Please put a ticket name in the subject of an email. Don’t force people to go to JIRA to find out what task your question is related to. Plus, those who can truly assist might skip your email

Re: Stable binary key representation

Guys, Isn't the main issue here that we cannot use the Identity Resolvers in BTrees in the 2.0 version? If yes, then we have to remove them no matter what. D. On Thu, Apr 6, 2017 at 1:23 PM, Sergi Vladykin wrote: > Binary key representation is stable when we always

Re: Stable binary key representation

Binary key representation is stable when we always have equal serialized bytes when the original keys are equal. Resolver allows you to have some extra info in the Key and equal Keys will be serialized into different bytes, which is wrong. Look at the example what you can do with resolvers: We

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

On Thu, Apr 6, 2017 at 2:52 AM, Alexey Goncharuk wrote: > Yes, this can happen if caches were created on different versions of > topology, because FairAffinityFunction is stateful and requires previous > affinity assignment state. > In this case we have to add

Re: Question: local cache on client nodes

Sergey, I think your suggestion makes sense. Please make sure that the exception thrown states that client side caches can only be configured on system startup. On Wed, Apr 5, 2017 at 5:43 AM, Sergey Chugunov wrote: > In that case I suggest the following solution

compute broadcast with PCL environment question

hi, Igniters. I have a question about compute broadcast behavior with peer class loading enabled. Look, my test schema was like: 1-jvm PureServerApp - pure server GG node. 2-jvm FirstComputeRunner - first compute runner node. 3-jvm SecondComputeRunner - second compute runner node. and my

[GitHub] ignite pull request #1755: IGNITE-4920 Fixed.

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/1755 IGNITE-4920 Fixed. LocalDeploymentSpi resources cleanup on spi.register() might clean resources from other tasks using delegating classloader. You can merge this pull request into a Git

Re: Distribution of keys to partitions

Guys, I replied in ticket. Overall I liked the changes but I think this needs additional elaboration. Please see https://issues.apache.org/jira/browse/IGNITE-4828 --Yakov 2017-03-31 20:09 GMT+03:00 Denis Magda : > Michael, thanks. > > I did minor improvements and merged them

Re: ask for a ticket

Hi, You can find such issues with priorities using Jira Filter. For example: https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20AND%20summary%20~%20%22transaction%22%20AND%20status%20!%3D%20Closed%20AND%20status%20!%3D%20Resolved%20ORDER%20BY%20priority%20DESC On Thu, Apr 6,

[jira] [Created] (IGNITE-4927) Write behind - need new mode without skipping values history

Yakov Zhdanov created IGNITE-4927: - Summary: Write behind - need new mode without skipping values history Key: IGNITE-4927 URL: https://issues.apache.org/jira/browse/IGNITE-4927 Project: Ignite

ask for a ticket

Igniters! Do smbd has got transaction related issue to do ? -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #1754: Ignite 3477 client hash index fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1754 Ignite 3477 client hash index fix DO NOT MERGE PR only to run tests on TC You can merge this pull request into a Git repository by running: $ git pull

Re: Apache Ignite 2.0 Release

I've prepared IGNITE-4349 - Discontinue the schema-import utility Anton, could you review my changes related to Ignite *build*? See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163 -- Alexey Kuznetsov

Re: IGNITE-4809

Aleksey, This issue is a part of a more global task: https://issues.apache.org/jira/browse/IGNITE-3478 which is currently being designed by the community [1], Sergi Vladykin is driving the process. For some reason, this ticket was not linked to the first issue, I've fixed that. Once we all agree

[GitHub] ignite pull request #1753: IGNITE-4898: Added ODBC installers paths to READM...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1753 IGNITE-4898: Added ODBC installers paths to README You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4898

[GitHub] ignite pull request #1752: ignite-2913 - SQL: EXISTS support added

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/1752 ignite-2913 - SQL: EXISTS support added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.5-p1

[GitHub] ignite pull request #1751: IGNITE-1977 Fixes IgniteSemaphore failover deadlo...

GitHub user vladisav opened a pull request: https://github.com/apache/ignite/pull/1751 IGNITE-1977 Fixes IgniteSemaphore failover deadlock/fail bug You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladisav/ignite ignite-1977

Re: IgniteSemaphore and failoverSafe flag

Hey Dmitry, sorry for the late reply, I'll try to bake a pr later during the day. Best regards, Vladisav On Tue, Apr 4, 2017 at 11:05 AM, Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: > Hi Vladislav, > > I see you're developing [1] for a while, did you have any chance to fix > it?

[jira] [Created] (IGNITE-4926) .NET: Join fails in LINQ when subquery is using Select clause

Sergey Stronchinskiy created IGNITE-4926: Summary: .NET: Join fails in LINQ when subquery is using Select clause Key: IGNITE-4926 URL: https://issues.apache.org/jira/browse/IGNITE-4926

[GitHub] ignite pull request #1750: IGNITE-4925 Fix IgniteCacheEntryListenerEagerTtlD...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1750 IGNITE-4925 Fix IgniteCacheEntryListenerEagerTtlDisabledTest.hronousEventsObjectKeyValue… You can merge this pull request into a Git repository by running: $ git pull

Re: Apache Ignite 2.0 Release

I have went through my issues and moved most of them to 2.1. However, the following looks very important: https://issues.apache.org/ jira/browse/IGNITE-4354 DML: BinaryObjectBuilder does not sort fields in some cases Alexander Paschenko, I think you have worked on field sorting, can you have a

Re: Apache Ignite 2.0 Release

I am almost done with DDL. It will be available for review in the nearest time. On Thu, Apr 6, 2017 at 1:38 PM, Vladimir Ozerov wrote: > Convenient filter to view your tickets (you must be logged in to JIRA): >

[jira] [Created] (IGNITE-4925) IgniteCacheEntryListenerEagerTtlDisabledTest.testSynchronousEventsObjectKeyValue test fails while invoking from IgniteBinaryCacheTestSuite

Evgenii Zhuravlev created IGNITE-4925: - Summary: IgniteCacheEntryListenerEagerTtlDisabledTest.testSynchronousEventsObjectKeyValue test fails while invoking from IgniteBinaryCacheTestSuite Key: IGNITE-4925

Re: Stable binary key representation

Even with my vast expirience I would never claim that I've seen "everything" :) What do you mean by stable binary key representation and how resolvers make it unstable? -Val On Thu, Apr 6, 2017 at 2:36 AM, Sergi Vladykin wrote: > Val, > > I know that you have really

Re: Stable binary key representation

It's reasonable to listen to Vladimir Ozerov and Alex Paschenko opinion before any removal. The identity resolvers were designed by them for specific use cases and, if I'm not mistaken, one is DML related. Folks, please join the conversation. Denis On Thursday, April 6, 2017, Sergi Vladykin

[GitHub] ignite pull request #1749: IGNITE-4524: Index direct lookup for SQL MIN() an...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1749 IGNITE-4524: Index direct lookup for SQL MIN() and MAX() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1717: IGNITE-4524: Index direct lookup for SQL function...

Github user skalashnikov closed the pull request at: https://github.com/apache/ignite/pull/1717 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Apache Ignite 2.0 Release

Convenient filter to view your tickets (you must be logged in to JIRA):

Re: Apache Ignite 2.0 Release

Folks, I would also encourage you to review all 2,0 tickets that are either assigned to you or submitted by you and move them to the next version (2.1) if you cannot complete them in the nearest time. Currently we have 554 opened tickets for 2.0. Let's make sure that we have about several dozens

[GitHub] ignite pull request #1748: IGNITE-4832: Service is deployed on client when s...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1748 IGNITE-4832: Service is deployed on client when service configuration is provided on startup. You can merge this pull request into a Git repository by running: $ git pull

IGNITE-1794 is ready for review

Dear sirs! Sorry for incorrect subject. https://github.com/apache/ignite/pull/1643 -- Forwarded message -- From: Вадим Опольский Date: 2017-03-24 15:48 GMT+03:00 Subject: ready for review IGNITE-933 To: dev@ignite.apache.org, Denis Magda

Re: Apache Ignite 2.0 Release

Hello community! Denis, issue IGNITE-1794 - Hibernate 5 Support has been ready for review from 24 March. The tests in Team City executed successfully. Vadim Opolski 2017-04-06 5:04 GMT+03:00 Denis Magda : > *Denis Magda:*

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

Yes, this can happen if caches were created on different versions of topology, because FairAffinityFunction is stateful and requires previous affinity assignment state. Generally, this can be fixed by introducing cache groups that use the same affinity and use this shared state across all caches.

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

Andrey, I did not know that FairAffinity can lead to this inconsistent behavior. AG can you please comment on this? Christos, Because it will complicate execution pipeline (and by that may be slowdown even collocated execution) and in case of different cluster groups we never will be

Re: Stable binary key representation

Val, I know that you have really vast experience in Ignite deployments and probably saw everything that can happen. Did you ever see identity resolvers use in real life? I guess no. Hibernate example is bad here, because if their key is unstable across multiple JVMs, it means that it was not

[jira] [Created] (IGNITE-4924) Visor CMD do not work in client mode

guoht created IGNITE-4924: - Summary: Visor CMD do not work in client mode Key: IGNITE-4924 URL: https://issues.apache.org/jira/browse/IGNITE-4924 Project: Ignite Issue Type: Bug

Re: Bug fix to IGNITE-4817

Thank you, Pavel! On 6 April 2017 at 10:35, Pavel Tupitsyn wrote: > Hi Sergey, good job, I've merged your changes to master branch! > See comments in JIRA. > > Thanks for the contribution! > > Pavel > > On Wed, Apr 5, 2017 at 11:32 PM, Guru Stron

[GitHub] ignite pull request #1747: Ignite-1267-1

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

[GitHub] ignite pull request #1739: Ignite-1267-1

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1739 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: IGNITE-2558 PR is ready to review (NearCacheConfiguration should not extend MutableConfiguration)

Maxim, I will take a look today or tomorrow. -Val On Tue, Apr 4, 2017 at 7:40 AM, Kozlov Maxim wrote: > Create ticket https://issues.apache.org/jira/browse/IGNITE-4910 < > https://issues.apache.org/jira/browse/IGNITE-4910> and fix PR. > > > 4 апр. 2017 г., в 17:06,

[GitHub] ignite pull request #1741: IGNITE-4914 distributing marshaller mappings for ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1741 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1746: Ignite 2466 1.8.6 OutOfMemory when PRIMARY_SYNC m...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1746 Ignite 2466 1.8.6 OutOfMemory when PRIMARY_SYNC mode is used You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Stable binary key representation

Alex, To be honest, I don't understand the reasoning behind the removal. I think resolvers provide good flexibility for different corner cases and it's a good thing to have them. Note that they can be applied not only to cache keys, but to any binary objects. Hibernate issue is actually a good

Re: IGNITE - 4760 : working in hibernate module

Denis, review please this test. The problem was recreated in the updating part ( //updating ). https://github.com/vadopolski/ignite/pull/1/files Changes supposed by Cameron Braid in threadLocalForCache method doesn't make the test successfully

[jira] [Created] (IGNITE-4923) .NET: ClientReconnected event fires on reconnect timeout

Pavel Tupitsyn created IGNITE-4923: -- Summary: .NET: ClientReconnected event fires on reconnect timeout Key: IGNITE-4923 URL: https://issues.apache.org/jira/browse/IGNITE-4923 Project: Ignite

Re: Bug fix to IGNITE-4817

Hi Sergey, good job, I've merged your changes to master branch! See comments in JIRA. Thanks for the contribution! Pavel On Wed, Apr 5, 2017 at 11:32 PM, Guru Stron wrote: > Hi guys, > > I've finished implementing bug fix to IGNITE-4817 .NET: Contains fails in >

[GitHub] ignite pull request #1745: IGNITE-4817

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1745 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Stable binary key representation

Denis, Can you suggest a use-case where identity resolver is needed (given that we agree that a key must contain only valuable fields)? 2017-04-05 22:08 GMT+03:00 Denis Magda : > Where do you want to remove the identity resolvers from? If it’s related > to the internals of

[GitHub] ignite pull request #1733: IGNITE-4885 .NET: Disallow abstract and open gene...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1733 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1738: IGNITE-4899 .NET: Review Dictionary usage in APIs

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1738 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is