[jira] [Created] (IGNITE-4846) .NET: Support complex type dictionaries in app.config configuration

Pavel Tupitsyn created IGNITE-4846: -- Summary: .NET: Support complex type dictionaries in app.config configuration Key: IGNITE-4846 URL: https://issues.apache.org/jira/browse/IGNITE-4846 Project: Igni

[jira] [Created] (IGNITE-4845) REST LOG API does not work when Ignite-log4j module is enabled

Sam created IGNITE-4845: --- Summary: REST LOG API does not work when Ignite-log4j module is enabled Key: IGNITE-4845 URL: https://issues.apache.org/jira/browse/IGNITE-4845 Project: Ignite Issue Type: Bu

[GitHub] ignite pull request #1643: IGNITE-1794

GitHub user vopolski opened a pull request: https://github.com/apache/ignite/pull/1643 IGNITE-1794 Fixed originally by Mykola Pereyma. Changed hibernate version to 5.2.7 and deleted ByteArrayType.java as per CI comments. You can merge this pull request into a Git repository by runn

[GitHub] ignite pull request #1642: Ignite-4828

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1642 Ignite-4828 Improve the distribution of keys within partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite IGNITE-4828 A

Re: Should we take care of Java 9 in Ignite 2.0 scope?

Referring to your report only the following API was removed completely. The rest is still deprecated and stowed in special JDK 9 modules. "org.apache.ignite.internal.processors.hadoop.HadoopClassLoader" -> "sun.misc.PerfCounter (JDK internal API (JDK removed internal API))”; "org.apache

Re: Should we take care of Java 9 in Ignite 2.0 scope?

Igniters, There are a few JDK internal APIs removed in JDK 9, that we use in ignite. We need to decide what to do with these dependencies. Here is a list of dependencies after using jdeps 2017-01-26 12:07 GMT+03:00 Anton Vinogradov : > Denis, > > I've created issue

prepare phase messages handlers question

Hi all! What is the point of sending GridDhtTxPrepareRequest and GridDhtTxPrepareResponse messages? What is the logic behind processDhtTxFinishRequest and processDhtTxPrepareResponse ? -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-3605

hello Igniters, i try to investigate bug in jmx metrics ticket: https://issues.apache.org/jira/browse/IGNITE-3605, wrote some comments there, can anyone hint me - what kind of changes are applicable here: 1. client node need to send "cacheMetrics" too, through TcpDiscoveryClientHeartbeatMessa

[jira] [Created] (IGNITE-4844) Get rid of cache async operations queue

Semen Boikov created IGNITE-4844: Summary: Get rid of cache async operations queue Key: IGNITE-4844 URL: https://issues.apache.org/jira/browse/IGNITE-4844 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4843) SQL: add support caches with different parallelizm degree within same query.

Andrew Mashenkov created IGNITE-4843: Summary: SQL: add support caches with different parallelizm degree within same query. Key: IGNITE-4843 URL: https://issues.apache.org/jira/browse/IGNITE-4843

Re: Ignite-4795 - ready for review

Done. 2017-03-20 16:30 GMT+03:00 Антон Чураев : > Dmitry, thank you! > > Could you please also change issue status to "Patch available". > > 2017-03-20 16:01 GMT+03:00 Дмитрий Рябов : > > > Hello, community. Please, review and/or suggest something about javadocs > of > > transactions. > > > > PR:

Re: Ignite-4795 - ready for review

Dmitry, thank you! Could you please also change issue status to "Patch available". 2017-03-20 16:01 GMT+03:00 Дмитрий Рябов : > Hello, community. Please, review and/or suggest something about javadocs of > transactions. > > PR: https://github.com/apache/ignite/pull/1630/files > > JIRA: https://i

Ignite-4795 - ready for review

Hello, community. Please, review and/or suggest something about javadocs of transactions. PR: https://github.com/apache/ignite/pull/1630/files JIRA: https://issues.apache.org/jira/browse/IGNITE-4795

Re: Write access to Apache Ignite repository

Ok, It seems that I've used github mirror instead of the project repository as an upstream. Fixed now. On Mon, Mar 20, 2017 at 1:12 PM, Igor Sapego wrote: > Thanks, I'll check it. > > On Mon, Mar 20, 2017 at 1:05 PM, Vyacheslav Daradur > wrote: > >> Maybe your key isn't added? >> >> https://peo

[GitHub] ignite pull request #1641: Ignite 4842

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1641 Ignite 4842 …not in local backup yet on atomic cache. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4842

[jira] [Created] (IGNITE-4842) IgniteCache.containsKey() may return false if entry is not in local backup yet on atomic cache

Dmitry Karachentsev created IGNITE-4842: --- Summary: IgniteCache.containsKey() may return false if entry is not in local backup yet on atomic cache Key: IGNITE-4842 URL: https://issues.apache.org/jira/browse/I

Re: transactions classes usage

Originating node is the node from which operation is initiated for a given key. Primary node, as its name implies, is a node which is primary for the key. Usually, an originating node is a client node. On Mon, Mar 20, 2017 at 2:30 PM, ALEKSEY KUZNETSOV wrote: > ah, what is the difference between

Re: transactions classes usage

ah, what is the difference between originating node and primary one ? пт, 17 мар. 2017 г. в 17:47, Alexander Fedotov : > Hi, > > GridNearTx*Request are sent from the originating node while > GridDhtTx*Request > are sent from the primary node. > If originating node is primary the same time, then o

Re: ignite-3682 - GridFunc: move all inner anonymous classes to separate top-level classes.

I've received answers in the issue. Ready for review. 2017-03-16 10:14 GMT+03:00 Vyacheslav Daradur : > Hello everyone. > > I have some questions about the issue https://issues.apache. > org/jira/browse/IGNITE-3682 > > 1) Can I do some minor refactoring of GridFunc class within this task? > (to

[jira] [Created] (IGNITE-4841) Improve TEXT Query Documentation

Daniel Siviter created IGNITE-4841: -- Summary: Improve TEXT Query Documentation Key: IGNITE-4841 URL: https://issues.apache.org/jira/browse/IGNITE-4841 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-4840) Remove GridQueryProcessor.onUndeploy() method

Vladimir Ozerov created IGNITE-4840: --- Summary: Remove GridQueryProcessor.onUndeploy() method Key: IGNITE-4840 URL: https://issues.apache.org/jira/browse/IGNITE-4840 Project: Ignite Issue Ty

Re: Write access to Apache Ignite repository

Thanks, I'll check it. On Mon, Mar 20, 2017 at 1:05 PM, Vyacheslav Daradur wrote: > Maybe your key isn't added? > > https://people.apache.org/keys/committer/isapego > > 2017-03-20 12:33 GMT+03:00 Igor Sapego : > > > Denis, > > > > I've checked again and I get this message when I try to push my p

Re: Write access to Apache Ignite repository

Maybe your key isn't added? https://people.apache.org/keys/committer/isapego 2017-03-20 12:33 GMT+03:00 Igor Sapego : > Denis, > > I've checked again and I get this message when I try to push my patch to > ignite-2.0 branch: > > remote: Permission to apache/ignite.git denied to isapego. > fatal:

Client got stucked on get operation

Hi all. We have 3 ignite servers. Server 1 works as standalone. Server 2 and 3 connects eachother as server but connects server 1 as client. In a point of the time server 3 got stucked at: at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:

[jira] [Created] (IGNITE-4839) Remove CacheTypeMetadata

Taras Ledkov created IGNITE-4839: Summary: Remove CacheTypeMetadata Key: IGNITE-4839 URL: https://issues.apache.org/jira/browse/IGNITE-4839 Project: Ignite Issue Type: Sub-task Comp

Re: Write access to Apache Ignite repository

Denis, I've checked again and I get this message when I try to push my patch to ignite-2.0 branch: remote: Permission to apache/ignite.git denied to isapego. fatal: unable to access 'https://github.com/apache/ignite.git/': The requested URL returned error: 403 Am I doing anything wrong? Do I use

[GitHub] ignite pull request #1639: IGNITE-4576 .NET: Rename IgniteConfiguration.Grid...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1639 --- 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-4838) NPE on execution of unknown internal task by name

Vasiliy Sisko created IGNITE-4838: - Summary: NPE on execution of unknown internal task by name Key: IGNITE-4838 URL: https://issues.apache.org/jira/browse/IGNITE-4838 Project: Ignite Issue Ty

Re: IgniteSemaphore and failoverSafe flag

I think re-creation should be handled by a user who will make sure that nobody else is currently executing the guarded logic before the re-creation. This is exactly the same semantics as with BrokenBarrierException for j.u.c.CyclicBarrier. 2017-03-17 2:39 GMT+03:00 Vladisav Jelisavcic : > Hi ever

[GitHub] ignite pull request #1640: ignite-4797: Added API for system allocated size ...

GitHub user kartiksomani opened a pull request: https://github.com/apache/ignite/pull/1640 ignite-4797: Added API for system allocated size in CacheMetrics Added getSystemAllocatedSize API (https://issues.apache.org/jira/browse/IGNITE-4797) to expose offHeap memory allocated for in

[GitHub] ignite pull request #1634: IGNITE-4834

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1634 --- 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: CacheStore and Transaction

I mean *CacheConfiguration.setAtomicityMode*[1] Because transactions makes a sense only for TRANSACTIONAL cache. [1]: https://apacheignite.readme.io/docs/transactions#section-atomicity-mode On Sun, Mar 19, 2017 at 11:14 PM, Vladislav Pyatkov wrote: > Hi > > Make sure are you using transactional