Re: documentation suggestions

Denis, Thanks for your comments. The pages I suggested have to do with the "getting started" or "how to's" for Ignite. Burying it inside of other docs will not make sense. That is why I suggested adding them under "Basic Concepts" section, i.e. keep them very visible. D. On Thu, Oct 5, 2017 at

[jira] [Created] (IGNITE-6559) Wrong JMX CacheClusterMetrics

Alexander Belyak created IGNITE-6559: Summary: Wrong JMX CacheClusterMetrics Key: IGNITE-6559 URL: https://issues.apache.org/jira/browse/IGNITE-6559 Project: Ignite Issue Type: Bug

Re: PRIMARY_SYNC+readFromBackup semantics

Val, do you have a fix in mind? On Thu, Oct 5, 2017 at 2:50 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > FULL_SYNC as default is not a solution. PRIMARY_SYNC/readFromBackup is > valid combination of parameters and useful in many scenarios. For example, > what if I have a repl

[GitHub] ignite pull request #2661: IGNITE-6307: Bug fix and new tests

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

[GitHub] ignite pull request #2629: IGNITE-6307: Remove new local entries from onHeap...

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

Re: PRIMARY_SYNC+readFromBackup semantics

FULL_SYNC as default is not a solution. PRIMARY_SYNC/readFromBackup is valid combination of parameters and useful in many scenarios. For example, what if I have a replicated cache and don't want to update all nodes synchronously? The point is that get() invoked after the put() in the same thread s

Re: documentation suggestions

WAL modes is documented - https://apacheignite.readme.io/v2.2/docs/ignite-persistence-23#section-wal-modes On Wed, Oct 4, 2017 at 2:07 PM, Denis Magda wrote: > Please see inline > > > On Oct 4, 2017, at 5:17 AM, Dmitriy Setrakyan > wrote: > > > > I would like to propose some changes to the Igni

Re: Identifying grid transactions

That's a very useful suggestion. Can it be supported for other APIs as well, not only transactions? -Val On Wed, Oct 4, 2017 at 12:47 PM, Vladimir Ozerov wrote: > +1 for withTag() > > ср, 4 окт. 2017 г. в 17:19, Yakov Zhdanov : > > > Really like .withTag() suggestion! > > > > --Yakov > > >

Re: Enhance persistent store paths: new persistent store folders naming

Hi Dmitriy, Good improvement and right in time, thanks! Thinking of a high level documentation, the user has to know: * how to start nodes from different clusters on a single box. They need to specify unique paths for storage files. * how to tackle the error described as Option 3 on wiki. * how

Re: documentation suggestions

Please see inline > On Oct 4, 2017, at 5:17 AM, Dmitriy Setrakyan wrote: > > I would like to propose some changes to the Ignite documentation: > > - Under Basic Concepts add the following pages: > - "How to load data” This should go to “Data Loading” or Streaming sections that appear at

[jira] [Created] (IGNITE-6558) Document WAL Modes

Denis Magda created IGNITE-6558: --- Summary: Document WAL Modes Key: IGNITE-6558 URL: https://issues.apache.org/jira/browse/IGNITE-6558 Project: Ignite Issue Type: Task Reporter: Deni

Re: Identifying grid transactions

+1 for withTag() ср, 4 окт. 2017 г. в 17:19, Yakov Zhdanov : > Really like .withTag() suggestion! > > --Yakov >

Enhance persistent store paths: new persistent store folders naming

Hi Igniters, Issue for improve persistent store paths https://issues.apache.org/jira/browse/IGNITE-6285 has been resolved. Thanks to Alexey G. and Yakov for review. Details of change are available in wiki https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#

[GitHub] ignite pull request #2803: IGNITE-6557: Fluky test fixed.

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/2803 IGNITE-6557: Fluky test fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-6557 Alternatively you can review a

Re: Ignite long term support (LTS) version policy?

Hi Dop, There are no such plans for that at the moment. Probably the community will come to this point at some time. For now, I can suggest you talk to companies that build enterprise solutions on top of Ignite. They provide guarantees you’re looking for. — Denis > On Oct 4, 2017, at 4:03 AM,

[jira] [Created] (IGNITE-6557) Test IgniteTxRemoveTimeoutObjectsTest has flaky fails

Vitaliy Biryukov created IGNITE-6557: Summary: Test IgniteTxRemoveTimeoutObjectsTest has flaky fails Key: IGNITE-6557 URL: https://issues.apache.org/jira/browse/IGNITE-6557 Project: Ignite

[GitHub] ignite pull request #2795: IGNITE-6550 Add new snapshot record type (Snapsho...

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

[GitHub] ignite pull request #2792: IGNITE-6547 Added ability log timestamp for wal t...

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

[GitHub] ignite pull request #2595: IGNITE-1.8.11 release

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

[GitHub] ignite pull request #2802: Ignite 12881

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/2802 Ignite 12881 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12881 Alternatively you can review and apply t

[GitHub] ignite pull request #2274: Ignite 5682

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

[GitHub] ignite pull request #2225: Ignite gg 12390

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

[GitHub] ignite pull request #2801: removed excluding ML from examples/src

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2801 removed excluding ML from examples/src You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite remove-ml-excluding Alterna

Re: Identifying grid transactions

Really like .withTag() suggestion! --Yakov

Re: Identifying grid transactions

On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > Hi, > > .withTag maybe? > Agree, withTag() looks much better.

Re: Logical Cache Documented

Hi, bigger B+ Tree = more operations to find a value. User may expect that cache having 20 entries (e.g. dictionary) will have great performance on get() and put(). But instead (if the 1 global cache group became default), such caches will take the same amount of time as the huge cache with milli

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

I'll personally would also greatly appreciate if ignite-core is build using (source and target) version of JDK 8. All contributors will be able to write code shorter and more expressively using code Java 8. ср, 4 окт. 2017 г. в 11:55, Yury Babak : > It`s true, now building of ML cause pain beca

[jira] [Created] (IGNITE-6556) setSchema() is case sensitive in the wrong way in Thin JDBC driver

Ilya Kasnacheev created IGNITE-6556: --- Summary: setSchema() is case sensitive in the wrong way in Thin JDBC driver Key: IGNITE-6556 URL: https://issues.apache.org/jira/browse/IGNITE-6556 Project: Ign

Re: Identifying grid transactions

No I meant just a string p.s. .withTag looks better On Wed, Oct 4, 2017 at 3:08 PM, Vladimir Ozerov wrote: > Sergey, > > Do you mean attaching something more than a single String? > > On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > > > Hi, > > > > .withTag maybe? > > > > 04/10/2017

Re: documentation suggestions

Dmitriy, There is a short description of WAL modes on the page: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood . On Wed, Oct 4, 2017 at 3:17 PM, Dmitriy Setrakyan wrote: > I would like to propose some changes to the Ignite documentation: > >- U

documentation suggestions

I would like to propose some changes to the Ignite documentation: - Under Basic Concepts add the following pages: - "How to load data" - "SQL vs Scan" - "SQL vs Key-Value" - more? - For persistence section, add the following pages: - Write-Ahead-Log (WAL)

[GitHub] ignite pull request #2800: IGNITE-6554: Atomic cache remove operations are n...

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

Re: Identifying grid transactions

Sergey, Do you mean attaching something more than a single String? On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > Hi, > > .withTag maybe? > > 04/10/2017 14:52, Sergey Kozlov пишет: > > Hi >> >> .withApplication and .withMetatData may narrow use case. Looks like . >> withDescription

Re: Identifying grid transactions

Hi, .withTag maybe? 04/10/2017 14:52, Sergey Kozlov пишет: Hi .withApplication and .withMetatData may narrow use case. Looks like . withDescription can have more sense and allow use write any information valuable for further debugging. On Wed, Oct 4, 2017 at 2:47 PM, Dmitriy Setrakyan wrote:

Re: Identifying grid transactions

Hi .withApplication and .withMetatData may narrow use case. Looks like . withDescription can have more sense and allow use write any information valuable for further debugging. On Wed, Oct 4, 2017 at 2:47 PM, Dmitriy Setrakyan wrote: > I would rename to "withMetadata()". > > On Wed, Oct 4, 2017

Re: Identifying grid transactions

I would rename to "withMetadata()". On Wed, Oct 4, 2017 at 2:31 PM, Vladimir Ozerov wrote: > Alex, > > I do not think we have such feature in the product at the moment. But this > could be very valuable addition. For example, we have somewhat similar task > for JDBC - to track applications that

Re: Identifying grid transactions

Alex, I do not think we have such feature in the product at the moment. But this could be very valuable addition. For example, we have somewhat similar task for JDBC - to track applications that use the driver [1]. We can think of adding a single optional string to transaction protocol, so that we

Re: Identifying grid transactions

Alexey, thanks a lot! This requires a change in application code. Is there a way to do it without that? Alexey 2017-10-04 13:22 GMT+03:00 Alexei Scherbakov : > Alexey, > > Simplest way: wrap IgniteTransactions instance returned by > ignite.transactions() with delegate using advanced logging capa

Ignite long term support (LTS) version policy?

Hi, I’m currently developing an application for my employer, and starting beginning of 2017, Ignite started at 1.8, and released 1.9 (Feb), 2.0 (Apr), 2.1 (Jul) and recently 2.2 (Sep), or about 2 - 3 months a version. And I can see good features added to every releases, together with bug fixes.

[jira] [Created] (IGNITE-6555) When a CacheStore with a @SpringResource annotated field is configured Ignite fails to start via igniteSpringBean

Alexandr Fedotov created IGNITE-6555: Summary: When a CacheStore with a @SpringResource annotated field is configured Ignite fails to start via igniteSpringBean Key: IGNITE-6555 URL: https://issues.apache.org/

Re: PRIMARY_SYNC+readFromBackup semantics

Val, Totally agreed. I think this can be easily fixed by setting FULL_SYNC as default sync mode. Actually, I do not understand why this is not done yet. 2017-10-04 12:09 GMT+03:00 Vladislav Pyatkov : > Hi Val, > > If we update local backup immediate synchronously when sending commit to > prima

Re: Identifying grid transactions

Alexey, Simplest way: wrap IgniteTransactions instance returned by ignite.transactions() with delegate using advanced logging capabilities for tx* methods, like current thread and stack trace. There is no notion of transaction parameters. 2017-10-04 12:40 GMT+03:00 Alexey Inozemtsev : > Igniter

Identifying grid transactions

Igniters, A team I'm working with uses Apache Ignite massively. There are many application modules using the cluster. We've faced a problem on how to identify the external app modules which keep transactions open in the grid. Right now we have to restart client nodes to get reed of them. Is there

[GitHub] ignite pull request #2798: IGNITE-6554: Atomic cache remove operations are l...

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

[GitHub] ignite pull request #2800: IGNITE-6554: Atomic cache remove operations are n...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2800 IGNITE-6554: Atomic cache remove operations are not logged into WAL You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ign

Ignite + Postgres Webinar

Hello Dev team, I will be broadcasting an Ignite + Postgres webinar tomorrow at 2PM EST. You can find all details in the link below: https://ignite.apache.org/events.html#webinar-postgres-apacher-ignitetm Please let me k

Re: PRIMARY_SYNC+readFromBackup semantics

Hi Val, If we update local backup immediate synchronously when sending commit to primary, this only partly removes questions about consistence view. But we always can to get other (unpredictable) value, because another transaction will be executed simultaneously from other threads. At the same ti

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

It`s true, now building of ML cause pain because currently we need excess build of ignite-core using JDK 8. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #2799: IGNITE-6536 node must fail when detects mapping s...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2799 IGNITE-6536 node must fail when detects mapping storage corruption You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache