[jira] [Created] (IGNITE-3199) .NET: ASP.NET Session-State Store Provider

Pavel Tupitsyn created IGNITE-3199: -- Summary: .NET: ASP.NET Session-State Store Provider Key: IGNITE-3199 URL: https://issues.apache.org/jira/browse/IGNITE-3199 Project: Ignite Issue Type:

Re: [apache/ignite] [IGNITE-2929] IgniteContext should not have type parameters (#740)

Dmitriy, Yakov, Alexey K., What are your thoughts?

Re: [apache/ignite] [IGNITE-2929] IgniteContext should not have type parameters (#740)

Yes this is a breaking change however it addresses a real problem. I was going to pick up the ticket had someone not already fixed this. Thanks for taking care of this. For what it's worth, the original "bug" causes more problems than any breaking change would to fix it. Also Valentin's note about

Re: Interested in this ticket IGNITE-2344

Sure Thank you Dmitriy !! Regards Saikat On Wed, May 25, 2016 at 2:03 AM, Dmitriy Setrakyan wrote: > Hi Saikat, > > Looks like this ticket was unassigned, so feel free to start on it. Feel > free to send your questions here. > > D. > > On Tue, May 24, 2016 at 10:34 AM,

[jira] [Created] (IGNITE-3200) Permgen leak in IgniteUtils.forName()

Vladimir Ozerov created IGNITE-3200: --- Summary: Permgen leak in IgniteUtils.forName() Key: IGNITE-3200 URL: https://issues.apache.org/jira/browse/IGNITE-3200 Project: Ignite Issue Type:

Re: Deadlock detection usage

Denis, I have made some minor edits. Please see if it makes sense. Thanks, -Prachi On Wed, May 25, 2016 at 9:43 AM, Dmitriy Setrakyan wrote: > I would make deadlock-detection into a separate page. This way it will be > more prominent and easier to access. > > I think we

RE: [jira] [Created] (IGNITE-3200) Permgen leak in IgniteUtils.forName()

Attached. -Original Message- From: Vladimir Ozerov (JIRA) [mailto:j...@apache.org] Sent: Wednesday, May 25, 2016 3:03 PM To: dev@ignite.apache.org Subject: [jira] [Created] (IGNITE-3200) Permgen leak in IgniteUtils.forName() Vladimir Ozerov created IGNITE-3200:

Re: [apache/ignite] [IGNITE-2929] IgniteContext should not have type parameters (#740)

In my view this change fixes a fundamental problem in the initial design, so I vote to have it merged. We should make it very clear to users that this change is incompatible with previous releases and provide a simple upgrade example in the documentation. On Wed, May 25, 2016 at 10:20 AM, Ahmad

New module

Hello everybody I wan to create a new module to integrate Ignite with Spring data, I was to the developer guide to see if there specific steps to build a module but I only saw the notice about the README and the license, but I have a very silly doubt but I want to do everything perfect, when you

[GitHub] ignite pull request: Docker image for Ignite 1.6.0

GitHub user zshamrock opened a pull request: https://github.com/apache/ignite/pull/757 Docker image for Ignite 1.6.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/zshamrock/ignite master Alternatively you can review and apply

Re: Deadlock detection usage

Parchi, Thanks a lot for the editing! Dmitriy, Maybe it’s better to introduce a table of content to Transactions documentation like it’s done for JVM tuning [1]? [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning > On

?????? [apache/ignite] [IGNITE-2929] IgniteContext should not have typeparameters (#740)

Hi, I wonder if we could add another class to implement the IgniteContext but without type parameter , f.e. IgniteContext2 or something else? -- -- ??: "Alexey Goncharuk";; : 2016??5??26??(??) 3:10 ??:

?????? [apache/ignite] [IGNITE-2929] IgniteContext should not have typeparameters (#740)

And the Apache Spark 2.0 maven repo will be available soon. The spark 2.0 will no longer use SparkContext but SparkSession, so should we also implement the new IgniteSession as the counterpart of SparkSession? -- -- ??: "mabiao";;

[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

[GitHub] ignite pull request: IGNITE-2538 RDD.isEmpty method should be over...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/741 --- 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

[jira] [Created] (IGNITE-3191) BinaryObjectBuilder: binary schema id depends on the order of fields addition

Denis Magda created IGNITE-3191: --- Summary: BinaryObjectBuilder: binary schema id depends on the order of fields addition Key: IGNITE-3191 URL: https://issues.apache.org/jira/browse/IGNITE-3191 Project:

[jira] [Created] (IGNITE-3193) IGFS: Better error logging for dual modes.

Vladimir Ozerov created IGNITE-3193: --- Summary: IGFS: Better error logging for dual modes. Key: IGNITE-3193 URL: https://issues.apache.org/jira/browse/IGNITE-3193 Project: Ignite Issue

IGNITE-2538 is merged to master

Biao Ma, I just merged your first fix in Apache Ignite. Congratulations and thanks for your effort! Looking forward to more contributions from you. -Val

Re: Deadlock detection usage

Denis, great doc! Thanks! On Tue, May 24, 2016 at 10:28 AM, Denis Magda wrote: > Andrey, thanks for additional details. The doc is updated > > https://apacheignite.readme.io/docs/transactions#deadlock-detection-in-pessimistic-transactions > < >

BigDecimal marshalling

Hi Igniters, Currently I'm working on the Decimal type implementation for the C++ client and when I was implementing it I've found that current marshalling of the BigDecimals seems to be broken as it assumes that scale of the BigDecimal value is always more than or equal to zero. However, scale

Re: New module

Hi Juan, All our modules have the same version. So when you create a new one, simply specify the same version that ignite-core has. -Val On Wed, May 25, 2016 at 9:44 AM, Juan Carlos Fiorenzano < jcfiorenzan...@gmail.com> wrote: > Hello everybody I wan to create a new module to integrate Ignite

Re: Cache metrics return incorrect values

Hmmm... Ok, every time when we perform put we go to offheap, becuase it can already contain this key. So my statement about one offheap get pere one cache.get is wrong. Anyway, get operation should update offheap gets metric. See usages of CacheMetricsImpl#onOffheapRead. On Wed, May 25, 2016

[jira] [Created] (IGNITE-3196) Marshaling works wrong for the BigDecimals that have negative scale

Igor Sapego created IGNITE-3196: --- Summary: Marshaling works wrong for the BigDecimals that have negative scale Key: IGNITE-3196 URL: https://issues.apache.org/jira/browse/IGNITE-3196 Project: Ignite

[GitHub] ignite pull request: Ignite 3190

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

[jira] [Created] (IGNITE-3195) Rebalancing: IgniteConfiguration.rebalanceThreadPoolSize is wrongly treated

Denis Magda created IGNITE-3195: --- Summary: Rebalancing: IgniteConfiguration.rebalanceThreadPoolSize is wrongly treated Key: IGNITE-3195 URL: https://issues.apache.org/jira/browse/IGNITE-3195 Project:

[jira] [Created] (IGNITE-3194) BinaryObjectException when web session attribute schema is changed

Valentin Kulichenko created IGNITE-3194: --- Summary: BinaryObjectException when web session attribute schema is changed Key: IGNITE-3194 URL: https://issues.apache.org/jira/browse/IGNITE-3194

Re: Cache metrics return incorrect values

Denis, I disagree. readOffheapPointer doesn't touch offheap get/put metrics deliberately. User should have exactly one offheap get operation per cache.get call. Vlad, as I can see offheap gets metric increments every time when get, contains, etc operations perform, so it should work. If you

[GitHub] ignite pull request: 7.5.23 2941 2942

Github user avinogradovgg closed the pull request at: https://github.com/apache/ignite/pull/750 --- 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: New module

Ok thank you On Wednesday, May 25, 2016, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Juan, > > All our modules have the same version. So when you create a new one, simply > specify the same version that ignite-core has. > > -Val > > On Wed, May 25, 2016 at 9:44 AM, Juan

[jira] [Created] (IGNITE-3198) TcpDiscoveryZookeeperIpFinderdoesn't handle timeout to connect to ZK

Sergey Kozlov created IGNITE-3198: - Summary: TcpDiscoveryZookeeperIpFinderdoesn't handle timeout to connect to ZK Key: IGNITE-3198 URL: https://issues.apache.org/jira/browse/IGNITE-3198 Project:

[jira] [Created] (IGNITE-3197) OverlappingFileLockException in marshaller context

Valentin Kulichenko created IGNITE-3197: --- Summary: OverlappingFileLockException in marshaller context Key: IGNITE-3197 URL: https://issues.apache.org/jira/browse/IGNITE-3197 Project: Ignite

[GitHub] ignite pull request: Ignite 2969 cas

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/756 Ignite 2969 cas You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2969-cas Alternatively you can review and apply

Re: Deadlock detection usage

I would make deadlock-detection into a separate page. This way it will be more prominent and easier to access. I think we can mention 2 topics on that page: - deadlock-free transactions - deadlock detection What do you think? D. On Wed, May 25, 2016 at 6:06 AM, Andrey Gura