RE: Does the Ignite C# client support distributed queues?

Hi Alexey, I think I need to be logged-in to vote for it. How do I get a credential to do that? Can you speak to my second question regards the plan for functional equivalence between C# & Java clients? Thanks, Raymond. *From:* Alexey Popov [mailto:tank2.a...@gmail.com] *Sent:* Saturda

Re: Request for Participation: The Right Metrics for the Right Project

+ Ignite dev Rafael, That’s a really useful project. I would use it for Ignite metrics analysis. How do you measure the pony-factor (contributors/committers breakdown per specific organization)? Is there a way to see user/dev list specific metrics such as most active participants (senders and

RE: ci.ignite.apache: Run all for patch (jira number)

The idea of doing so arose after I uploaded the changed patch second time and it didn't appear in teamcity to run against (changes). Should automatic build triggering work ? Anyway, I'll go for patch then. -Original Message- From: Dmitry Pavlov [mailto:dpavlov@gmail.com] Sent: Satur

Re: Documentation for GA Grid: GA library to Apache Ignite

Denis, Up on logging in, I do not see the Admin panel that you described. I have attached a screen shot for you review. There is only 'Suggest Edits' option. Is there something I missed? Please advise. Be

Re: ci.ignite.apache: Run all for patch (jira number)

Hi Cergey, for pull requests I use pull//head branch specification in changes field (e.g pull/2970/head) and https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll run configuration. Recently we've updated link on GitHub page so new contributors can see correct link. Not

[jira] [Created] (IGNITE-7092) Deprecate embedded mode in IgniteRDD

Valentin Kulichenko created IGNITE-7092: --- Summary: Deprecate embedded mode in IgniteRDD Key: IGNITE-7092 URL: https://issues.apache.org/jira/browse/IGNITE-7092 Project: Ignite Issue Typ

Re: Deprecate IgniteRDD in embedded mode

Ticket created: https://issues.apache.org/jira/browse/IGNITE-7092 -Val On Thu, Nov 30, 2017 at 5:01 PM, Denis Magda wrote: > Val, > > Sounds reasonable to me. The fewer useless and potentially harmful > features or “switches” we have in Ignite the clear it will be for the user > how to use us i

[GitHub] ignite pull request #3130: IGNITE-6565: Use long type for size and keySize i...

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/3130 IGNITE-6565: Use long type for size and keySize in cache metrics https://issues.apache.org/jira/browse/IGNITE-6565 You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3129: Fixed DataStructures restore from snapshot

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3129 Fixed DataStructures restore from snapshot You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13029 Alternative

Fwd: [jira] [Created] (IGNITE-7083) Reduce memory usage of CachePartitionFullCountersMap

Ignite, especially Sam and Alex G., what’d you think about this? — Denis > Begin forwarded message: > > From: "Sunny Chan (JIRA)" > Subject: [jira] [Created] (IGNITE-7083) Reduce memory usage of > CachePartitionFullCountersMap > Date: November 30, 2017 at 8:31:01 PM PST > To: dev@ignite.apache

Re: Time to drop Java 7?

Excellent, let's do it! пт, 1 дек. 2017 г. в 20:43, Denis Magda : > > Is my understanding correct, that the level of the VM for the source code > > will be 8? > > Exactly! > > — > Denis > > > On Dec 1, 2017, at 3:06 AM, Dmitry Pavlov wrote: > > > > +1. > > > > I am sincerely glad that we are rea

[GitHub] ignite pull request #3084: IGNITE-7007: Code cleanups.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3084 ---

Re: Are there any access control for ignite rest api

Hi, What’s Ignite Access Control? I’ve never heard about this tool/component. — Denis > On Dec 1, 2017, at 8:00 AM, kcmvp wrote: > > Hi All, > > Are there any access control fro Ignite Access Control? For my case I just > want get related rest api can be accessed ? > Of course it's better to

Re: Ignite Logger & logging file config output

Alexey, Thanks, looks good to me too. Let’s merge the changes into the master. — Denis > On Dec 1, 2017, at 6:35 AM, Alexey Popov wrote: > > Yes, it is implemented for all Ignite loggers. > However, some loggers (Slf4jLogger) does not have logging file configuration, > so they show less deta

Re: Documentation for GA Grid: GA library to Apache Ignite

Akmal, yes, the updates need to be checked: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document An actual reiview though can take place before or after a doc goes online. Turik, You can edit the page directly.

Re: Time to drop Java 7?

> Is my understanding correct, that the level of the VM for the source code > will be 8? Exactly! — Denis > On Dec 1, 2017, at 3:06 AM, Dmitry Pavlov wrote: > > +1. > > I am sincerely glad that we are ready to do this! > > Is my understanding correct, that the level of the VM for the source

Re: ci.ignite.apache: Run all for patch (jira number)

It’s possible but requires you to create a branch and pass its name into TeamCity: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file

[GitHub] ignite pull request #3128: IGNITE-7091: PDS Compatibilty: Assertion error in...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3128 IGNITE-7091: PDS Compatibilty: Assertion error in case serializer V1 Flaky failure fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[jira] [Created] (IGNITE-7091) PDS Compatibilty: Assertion error in case serializer V1 is found and there is no next segment to read in WAL iterator

Dmitriy Pavlov created IGNITE-7091: -- Summary: PDS Compatibilty: Assertion error in case serializer V1 is found and there is no next segment to read in WAL iterator Key: IGNITE-7091 URL: https://issues.apache.org/

[GitHub] ignite pull request #3127: Ignite-6339-mmap

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

[jira] [Created] (IGNITE-7090) Semaphore Stuck when no acquirers to assign permit

Tim Onyschak created IGNITE-7090: Summary: Semaphore Stuck when no acquirers to assign permit Key: IGNITE-7090 URL: https://issues.apache.org/jira/browse/IGNITE-7090 Project: Ignite Issue Typ

[GitHub] ignite pull request #3126: Ignite-2.1.8.b2

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

[GitHub] ignite pull request #3125: IGNITE-6338 .NET: Thin client: LINQ

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3125 IGNITE-6338 .NET: Thin client: LINQ You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6338 Alternatively you can revie

[GitHub] ignite pull request #3124: IGNITE-6425: Races during transaction finalizatio...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3124 IGNITE-6425: Races during transaction finalization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6425-maste

Are there any access control for ignite rest api

Hi All, Are there any access control fro Ignite Access Control? For my case I just want get related rest api can be accessed ? Of course it's better to have fine control -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

RE: Does the Ignite C# client support distributed queues?

Hi Raymond, You are right, distributed queues require changes at Ignite core. https://issues.apache.org/jira/browse/IGNITE-2701 It was created almost 1 year ago. Please vote for this feature. As far as I know there is no plan/schedule for it. Thank you, Alexey From: Raymond Wilson Sent: Friday

Re: Internal problems requiring graceful node shutdown, reboot, etc.

Dmitry, Seems, we found that it's impossible to specify one action for all cases, but it's a good idea to allow user to decide what to do. We should make something like interface IgniteFailureHandler { IgniteFailureAction onFailure(IgniteFailureCause cause); } public enum IgniteFailureAction

[jira] [Created] (IGNITE-7089) .NET: Thin client: LINQPad example

Pavel Tupitsyn created IGNITE-7089: -- Summary: .NET: Thin client: LINQPad example Key: IGNITE-7089 URL: https://issues.apache.org/jira/browse/IGNITE-7089 Project: Ignite Issue Type: Improveme

RE: Ignite Logger & logging file config output

Yes, it is implemented for all Ignite loggers. However, some loggers (Slf4jLogger) does not have logging file configuration, so they show less details. Thank you, Alexey From: Nikolai Tikhonov Sent: Friday, December 1, 2017 5:21 PM To: dev@ignite.apache.org Subject: Re: Ignite Logger & logging

[GitHub] ignite pull request #3123: IGNITE-6868 nodeId type fixed, unused methods rem...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3123 IGNITE-6868 nodeId type fixed, unused methods removed You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-6868-

Re: Documentation for GA Grid: GA library to Apache Ignite

Updates need to be checked and approved before going live? On 1 December 2017 at 04:11, techbysample wrote: > Denis, > > Thanks. In review, I noticed that when I edit page: > > "https://apacheignite.readme.io/v2.3/docs/genetic-algorithms";, my updates > do > not appear instantly. > > Is this th

Re: Ignite Logger & logging file config output

Alexey, Looks cool and helpful! I understand correctly that improvement is implemented for all type of loggers which Ignite supports? On Fri, Dec 1, 2017 at 5:18 PM, Alexey Popov wrote: > Hi Denis, > > https://issues.apache.org/jira/browse/IGNITE-6971 > > Sample quite=true output: > > [17:16:41

RE: Ignite Logger & logging file config output

Hi Denis, https://issues.apache.org/jira/browse/IGNITE-6971 Sample quite=true output: [17:16:41]__ [17:16:41] / _/ ___/ |/ / _/_ __/ __/ [17:16:41] _/ // (7 7// / / / / _/ [17:16:41] /___/\___/_/|_/___/ /_/ /___/ [17:16:41] [17:16:41] ver. 2.4.0-S

Re: Thin Client Protocol documentation

There are no legacy formats. JDBC and ODBC clients are not "legacy", quite the opposite. In future we may even want to combine JDBC Thin and general-purpose Thin clients since they have a lot in common. So let's keep the handshake format consistent across clients. > exceptions for message formats

[jira] [Created] (IGNITE-7088) Wrong implementation of DIRECT comparator for ordering cache start operations

Evgenii Zhuravlev created IGNITE-7088: - Summary: Wrong implementation of DIRECT comparator for ordering cache start operations Key: IGNITE-7088 URL: https://issues.apache.org/jira/browse/IGNITE-7088

[GitHub] ignite pull request #3122: Ignite-2.4.1-p1

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3122 Ignite-2.4.1-p1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p1 Alternatively you can review and app

Re: Internal problems requiring graceful node shutdown, reboot, etc.

HI Dmitry, I do not think it is good idea to mix failures of different threads into a single event type. - Practice shows that the most common source of problem is exchange thread - if disco worker has died, not will be excluded from topology safely - "nio-acceptor" can be spawn from multiple plac

[GitHub] ignite pull request #3121: IGNITE-7085 When PDS is enabled and IGNITE_BINARY...

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/3121 IGNITE-7085 When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS is set and IgniteCache#put is called node hangs CI You can merge this pull request into a Git repository by running: $ g

[jira] [Created] (IGNITE-7087) Ignite.destroyCache leave cache serialized config and prevent from repeatable cache creation.

Stanilovsky Evgeny created IGNITE-7087: -- Summary: Ignite.destroyCache leave cache serialized config and prevent from repeatable cache creation. Key: IGNITE-7087 URL: https://issues.apache.org/jira/browse/IGNI

[GitHub] ignite pull request #3120: IGNITE-6997 .NET: Thin client: Move ClientStatus ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3120 ---

[jira] [Created] (IGNITE-7086) Backups are not updated when ReadFromBackup=true and ReadThrough happens.

Andrew Mashenkov created IGNITE-7086: Summary: Backups are not updated when ReadFromBackup=true and ReadThrough happens. Key: IGNITE-7086 URL: https://issues.apache.org/jira/browse/IGNITE-7086 Pro

Re: Time to drop Java 7?

+1. I am sincerely glad that we are ready to do this! Is my understanding correct, that the level of the VM for the source code will be 8? пт, 1 дек. 2017 г. в 13:32, Andrey Gura : > Good news for everyone ) > > 30 нояб. 2017 г. 11:29 PM пользователь "Dmitriy Setrakyan" < > dsetrak...@apache.or

Re: New Compatibility Testing Framework module in the project

Hi Igniters, recently I’ve made several updates in the framework. - Now within the test, user can declare an extended classpath (e.g. use ignite-indexing). - Dumping classpath was added in case detached jvm node startup failed or hangs. In second case stack trace is additionally dumped. - Nod

[jira] [Created] (IGNITE-7085) When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS property is set and IgniteCache#put is called a node hangs

Alexandr Fedotov created IGNITE-7085: Summary: When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS property is set and IgniteCache#put is called a node hangs Key: IGNITE-7085 URL: https://issues.apache.or

RE: Thin Client Protocol documentation

Pavel, I believe ClientListenerNioListener.onHandshake() could support more than one Handshake request format (be backward compatible), for instance, if we will have a new handshake code = 0xABCD that differs from 0x01 byte. It is a design vs architecture question. I can’t understand why the

Re: Time to drop Java 7?

Good news for everyone ) 30 нояб. 2017 г. 11:29 PM пользователь "Dmitriy Setrakyan" < dsetrak...@apache.org> написал: > +1 > > On Thu, Nov 30, 2017 at 11:29 AM, Denis Magda wrote: > > > Igniters, > > > > Considering that we’re going to support Java 9 in the next release and > > hitting several l

[GitHub] ignite pull request #3120: IGNITE-6997 .NET: Thin client: Move ClientStatus ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3120 IGNITE-6997 .NET: Thin client: Move ClientStatus to public API You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6997

[GitHub] ignite pull request #3119: IGNITE-7002 .NET: Add cross-platform examples on ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3119 IGNITE-7002 .NET: Add cross-platform examples on .NET Core You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7002