[jira] [Created] (IGNITE-3519) Web console: add ability to specify a node filter in start caches configuration

Pavel Konstantinov created IGNITE-3519: -- Summary: Web console: add ability to specify a node filter in start caches configuration Key: IGNITE-3519 URL: https://issues.apache.org/jira/browse/IGNITE-3519

Rework "withAsync" in Apache 2.0

Hi folks, There was a discussion about not very good "withAsync()" API design [1]. As we are approaching Ignite 2.0 it is a good time to rework it. My considerations on how good API should look like and how should it be implemented: 1) Sync and async must be *different interfaces*. 2) All async m

[jira] [Created] (IGNITE-3518) Examples fail to build, can't find resource: ignite-apache-license-gen

Matt Stump created IGNITE-3518: -- Summary: Examples fail to build, can't find resource: ignite-apache-license-gen Key: IGNITE-3518 URL: https://issues.apache.org/jira/browse/IGNITE-3518 Project: Ignite

[jira] [Created] (IGNITE-3517) Modify build instructions to increase PermGen

Matt Stump created IGNITE-3517: -- Summary: Modify build instructions to increase PermGen Key: IGNITE-3517 URL: https://issues.apache.org/jira/browse/IGNITE-3517 Project: Ignite Issue Type: Bug

Re: IGNITE-2294 implementation details

I'd prefer to do MERGE operation last because in H2 it is not standard ANSI SQL MERGE. Or may be not implement it at all, or may be contribute ANSI correct version to H2, then implement it on Ignite. Need to investigate the semantics deeper before making any decisions here. Lets start with simple

Re: Ignite monitoring

Andrey, Is Web Console you are talking about the same thing as GridGain Web Console (http://ignite.apache.org/addons.html#web-console)? If yes it has monitoring tab which allows to monitor some JVM and cache metrics ( https://console.gridgain.com/monitoring). As for me, Visor command line tool do

[GitHub] ignite pull request #876: IGNITE-3516

GitHub user kromulan opened a pull request: https://github.com/apache/ignite/pull/876 IGNITE-3516 H2 Indexing unregister cache does not call TableDescriptor's GridH2Table close and optionally GridLuceneIndex close, which causes OFFHEAP_TIERED cache to leak memory. You can merge th

[jira] [Created] (IGNITE-3516) H2 Indexing unregisterCache method does not cleanup resources and causes memory leak with OFFHEAP_TIERED cache mode cache.

Krome Plasma created IGNITE-3516: Summary: H2 Indexing unregisterCache method does not cleanup resources and causes memory leak with OFFHEAP_TIERED cache mode cache. Key: IGNITE-3516 URL: https://issues.apache.org

Re: Converting TreeMap to BinaryObject causes ClassCastException (IGNITE-2852)

Hi Denis, thanks for clarifying. I'll take a look around Jira instead. Thanks Jens On Wed, Jul 20, 2016 at 1:45 PM, Denis Magda wrote: > Hi Jens, > > This is not the best candidate for the first contribution and presently I > don’t think that this feature should be supported at all. > > I woul

Re: ReadWriteUpdateLock

Vova, we discuss this without having any numbers. Any real-life use case? --Yakov 2016-07-20 9:48 GMT+03:00 Vladimir Ozerov : > I believe this could be a useful addition to Ignite. RWU-locks are not > widely-spread in Java. But for example in .NET this is a base concurrency > primitive. Of cours

[GitHub] ignite pull request #875: IGNITE-3515

GitHub user kromulan opened a pull request: https://github.com/apache/ignite/pull/875 IGNITE-3515 Null check for sync object added to IgniteSemaphore implementation stop method. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kro

[jira] [Created] (IGNITE-3515) NullPointerException when stopping IgniteSemaphore and no method has been called previously to initialize semaphore with initializeSemaphore().

Krome Plasma created IGNITE-3515: Summary: NullPointerException when stopping IgniteSemaphore and no method has been called previously to initialize semaphore with initializeSemaphore(). Key: IGNITE-3515 URL: htt

[GitHub] ignite pull request #874: IGNITE-1433 .NET: Add Java stack trace to IgniteEx...

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

[jira] [Created] (IGNITE-3514) CPP: JVM crash on some "Failed to start SPI" exception.

Igor Sapego created IGNITE-3514: --- Summary: CPP: JVM crash on some "Failed to start SPI" exception. Key: IGNITE-3514 URL: https://issues.apache.org/jira/browse/IGNITE-3514 Project: Ignite Issue

Re: Converting TreeMap to BinaryObject causes ClassCastException (IGNITE-2852)

Hi Jens, This is not the best candidate for the first contribution and presently I don’t think that this feature should be supported at all. I would recommend you picking up one of the tickets with “newbie” filter. https://issues.apache.org/jira/issues/?filter=12338037

Re: Ignite 2.0 tasks/roadmap

I am allowed to flip-flop on my opinions every now and then :) > On Jul 20, 2016, at 11:06 AM, Pavel Tupitsyn wrote: > > Dmitriy, you have agreed with me in the old thread, and now you don't? > Binarylizable (current) is longer than Binarizable (proposed). > > On Wed, Jul 20, 2016 at 10:24 AM,

Re: IGNITE-2294 implementation details

Like the idea of merge and insert. I need more time to think about the API changes. Sergi, what do you think? Dmitriy On Jul 20, 2016, at 12:36 PM, Alexander Paschenko wrote: >> Thus, I suggest that we implement MERGE as a separate operation backed by >> putIfAbsent operation, while INSER

[GitHub] ignite pull request #874: IGNITE-1433 .NET: Add Java stack trace to IgniteEx...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/874 IGNITE-1433 .NET: Add Java stack trace to IgniteException You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1433 Altern

[GitHub] ignite pull request #294: IGNITE-1433 .Net: Add IgniteException.JavaStackTra...

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

[jira] [Created] (IGNITE-3513) Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method

Denis Magda created IGNITE-3513: --- Summary: Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method Key: IGNITE-3513 URL: https://issues.apache.org/jira/browse/IGNITE-3513 Projec

[jira] [Created] (IGNITE-3512) .NET: IBinaryObject.ToBuilder loses type name

Pavel Tupitsyn created IGNITE-3512: -- Summary: .NET: IBinaryObject.ToBuilder loses type name Key: IGNITE-3512 URL: https://issues.apache.org/jira/browse/IGNITE-3512 Project: Ignite Issue Type

Re: Ignite monitoring

Igor, Ignite does not have monitoring in Web Console, only Configuration and SQL. But command-line Visor in Ignite have some monitoring features and can be used to add new. On Wed, Jul 20, 2016 at 1:19 AM, Igor Rudyak wrote: > Are there any documentation regarding how to use Ignite web console

Re: IGNITE-2294 implementation details

> Thus, I suggest that we implement MERGE as a separate operation backed by > putIfAbsent operation, while INSERT will be implemented via put. Sorry, of course I meant that MERGE has to be put-based, while INSERT has to be putIfAbsent-based. 2016-07-20 12:30 GMT+03:00 Alexander Paschenko : > Hel

IGNITE-2294 implementation details

Hell Igniters, In this thread I would like to share and discuss some thoughts on DML operations' implementation, so let's start and keep it here. Everyone is of course welcome to share their suggestions. For starters, I was thinking about semantics of INSERT. In traditional RDBMSs, INSERT works o

Re: Ignite 2.0 tasks/roadmap

Dmitriy, you have agreed with me in the old thread, and now you don't? Binarylizable (current) is longer than Binarizable (proposed). On Wed, Jul 20, 2016 at 10:24 AM, Dmitriy Setrakyan wrote: > > > > > On Jul 20, 2016, at 9:17 AM, Pavel Tupitsyn > wrote: > > > > How about renaming Binarylizabl

Re: Ignite 2.0 tasks/roadmap

> On Jul 20, 2016, at 9:17 AM, Pavel Tupitsyn wrote: > > How about renaming Binarylizable interface? > > http://apache-ignite-developers.2346864.n4.nabble.com/Naming-Binarylizable-td4592.html Pavel, I would not rename. The name you are suggesting is very hard to pronounce. > > On Sat, Jul