[jira] [Created] (IGNITE-6377) MemoryPolicyInitializationTest fails with OOME

Alexey Goncharuk created IGNITE-6377: Summary: MemoryPolicyInitializationTest fails with OOME Key: IGNITE-6377 URL: https://issues.apache.org/jira/browse/IGNITE-6377 Project: Ignite

[GitHub] ignite pull request #2660: IGNITE-6375

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2660 IGNITE-6375 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6375 Alternatively you can review and apply these

[GitHub] ignite pull request #2639: IGNITE-6314 Tests fix.

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

[GitHub] ignite pull request #2635: IGNITE-6340 : Fixed creation of client cache on s...

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

[GitHub] ignite pull request #2659: Ignite 1.9.6 b3

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2659 Ignite 1.9.6 b3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.6-b3 Alternatively you can review and

[jira] [Created] (IGNITE-6379) CacheExchangeMessageDuplicatedStateTest fails in master

Alexey Goncharuk created IGNITE-6379: Summary: CacheExchangeMessageDuplicatedStateTest fails in master Key: IGNITE-6379 URL: https://issues.apache.org/jira/browse/IGNITE-6379 Project: Ignite

Re: [VOTE] Apache Ignite 2.2.0 RC1

Denis, As far as DML, I debugged the problem. Currently we wrap key fields in a wrapper type. This is done for two reasons: 1) This is absolutely must for composite primary keys 2) To avoid clashes with other tables, should we decide to support CREATE TABLE on existing caches. E.g., without it if

[jira] [Created] (IGNITE-6380) Exception should be thrown on cache creation attempt inside transaction

Yakov Zhdanov created IGNITE-6380: - Summary: Exception should be thrown on cache creation attempt inside transaction Key: IGNITE-6380 URL: https://issues.apache.org/jira/browse/IGNITE-6380 Project:

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

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2661 IGNITE-6307: Bug fix and new tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-6307-ignite-2.1 Alternatively you

[jira] [Created] (IGNITE-6378) Web console: Demo mode panel hide part of affix panel.

Vasiliy Sisko created IGNITE-6378: - Summary: Web console: Demo mode panel hide part of affix panel. Key: IGNITE-6378 URL: https://issues.apache.org/jira/browse/IGNITE-6378 Project: Ignite

Re: Persistence per memory policy configuration

> I like the idea of having PersistentMemoryPolicy configuration class. I like the idea, too. --Yakov

Re: Persistence per memory policy configuration

>>Can we have separate MemoryPolycy for every CacheGroup? In that case we could auto generate MemoryPolycy based on CacheGroup settings and have a "cache level" persistence settings. >>We can use some kind of MemoryPolicyTemplate to add default values and even re-use existing MemoryPolicy if all

Re: Expiry policy for Cache.invoke

Val, Sorry, I may be didn't formulate the issue clearly. Other than predefined expiry policies (like CreatedExpiryPolicy, AccessedExpiryPolicy, etc) you can provide a custom expiry policy by calling setExpiryPolicyFactory(Factory)

Re: Expiry policy for Cache.invoke

Dmitriy, You are right about transactions, but the spec describes invoke, so, if it specifies some behavior in general, then it should be followed in both cases. Here is the most relevant part I could find in the spec:

[GitHub] ignite pull request #2658: ignite-5960 cont counter null if nobody listens

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2658 ignite-5960 cont counter null if nobody listens You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5960-1 Alternatively you

[GitHub] ignite pull request #2622: Ignite-1.9.6.b3

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

[jira] [Created] (IGNITE-6385) Offheap page eviction is broken in case loading data without data streamer

Ivan Rakov created IGNITE-6385: -- Summary: Offheap page eviction is broken in case loading data without data streamer Key: IGNITE-6385 URL: https://issues.apache.org/jira/browse/IGNITE-6385 Project:

[jira] [Created] (IGNITE-6383) SQL: review date/time format

Vladimir Ozerov created IGNITE-6383: --- Summary: SQL: review date/time format Key: IGNITE-6383 URL: https://issues.apache.org/jira/browse/IGNITE-6383 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6382) .NET: Set up NDepend analysis on TeamCity

Pavel Tupitsyn created IGNITE-6382: -- Summary: .NET: Set up NDepend analysis on TeamCity Key: IGNITE-6382 URL: https://issues.apache.org/jira/browse/IGNITE-6382 Project: Ignite Issue Type:

[GitHub] ignite pull request #2663: Ignite 3084 - pre alpha to share with AV

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2663 Ignite 3084 - pre alpha to share with AV You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-3084 Alternatively you can

[GitHub] ignite pull request #2662: IGNITE-6258 .NET: Thin client: Define metadata ex...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2662 IGNITE-6258 .NET: Thin client: Define metadata exchange protocol You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Ignite.NET static analysis with NDepend

Igniters, NDepend [1] has contacted me and provided us with build machine licenses for their tool. I've played with it for some time and it looks promising, see my blog post [2] for details. There is TeamCity support in form of a plugin [3], I've filed a ticket [4] to set it up. (We already have

[GitHub] ignite pull request #1611: Rebalancing optimizations.

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

Re: sql documentation

Denis, Thanks a lot for the link. It's very helpful to split "function part" to more specific like 'string', 'numeric', etc. the main reason to separate "Java Developer" as an independent part because it's about a mix between Java and SQL code. It's about classes, methods, annotation, GC, etc.

[jira] [Created] (IGNITE-6381) add support Scala 2.12 in libs org.apache.ignite.scalar

AlexZyryanov created IGNITE-6381: Summary: add support Scala 2.12 in libs org.apache.ignite.scalar Key: IGNITE-6381 URL: https://issues.apache.org/jira/browse/IGNITE-6381 Project: Ignite

[GitHub] ignite pull request #2646: IGNITE-6330: Implemented closing of ODBC and JDBC...

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

[GitHub] ignite pull request #2664: For testing.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2664 For testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12001-2.1.5 Alternatively you can review and

[GitHub] ignite pull request #2665: Ignite-gg-12773

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

[jira] [Created] (IGNITE-6384) Introduce API to monitor pending locks and transactions

Ilya Lantukh created IGNITE-6384: Summary: Introduce API to monitor pending locks and transactions Key: IGNITE-6384 URL: https://issues.apache.org/jira/browse/IGNITE-6384 Project: Ignite

[GitHub] ignite pull request #2666: IGNITE-6385 Offheap page eviction doesn't work if...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2666 IGNITE-6385 Offheap page eviction doesn't work if data is loaded without data streamer You can merge this pull request into a Git repository by running: $ git pull

Re: Static code analysis for Java

AFIK, we can run on TC same code analyzer that built in IDEA. See: CodeCoverageResults https://confluence.jetbrains.com/display/TCD10/Working+with+Build+Results#WorkingwithBuildResults-CodeCoverageResults Code Inspection

Re: Static code analysis for Java

Yakov, You might also wish to consider lgtm.com, which is already analysing Ignite builds ( https://lgtm.com/projects/g/apache/ignite/ ). It has found a number of issues, some of which have been fixed through https://issues.apache.org/jira/browse/IGNITE-5805 lgtm also supports the option of

Re: Static code analysis for Java

Yes, we can run IDEA inspections, and this is the simplest thing to do, since TeamCity already has this step available. On Thu, Sep 14, 2017 at 7:05 PM, Alexey Kuznetsov wrote: > AFIK, we can run on TC same code analyzer that built in IDEA. > > See: > >

[jira] [Created] (IGNITE-6386) Introduction of distributed neural networks.

Yury Babak created IGNITE-6386: -- Summary: Introduction of distributed neural networks. Key: IGNITE-6386 URL: https://issues.apache.org/jira/browse/IGNITE-6386 Project: Ignite Issue Type: New

Static code analysis for Java

Guys, I remember we tried some static code analysis tools for Java (a bit awkward not having one yet), but we did not setup regular checks. I want to return to this. As result I would like to have code analysis tool running on TC on daily basis and also established process to review and fix code

Re: Static code analysis for Java

Wow, Seems, that's what we were looking for! On Thu, Sep 14, 2017 at 6:26 PM, Malcolm Taylor wrote: > Yakov, > > You might also wish to consider lgtm.com, which is already analysing > Ignite > builds ( https://lgtm.com/projects/g/apache/ignite/ ). > It has found a number of

Re: Monitoring of active transactions

It seems that the community (including me) really would like to see this feature in Ignite. Ilya, can you create a ticket and submit it for review? D. On Fri, Sep 8, 2017 at 7:15 AM, Anton Vinogradov wrote: > Ilya, > > We extremely need this! > > Txs and Locks info should be

Re: Persistence per memory policy configuration

Vladimir, The configuration would look like so: IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setMemoryConfiguration(new MemoryConfiguration() .setMemoryPolicies( new MemoryPolicyConfiguration().setName("InMemory").setMaxSize(...), new

Ignite Benchmarking Rules

Hi, Igniters. Recently I’ve done some research in benchmarks for Ignite, and noticed that we don’t have any rules for running benchmarks and collecting result from them. Although sometimes we have tasks, which results need to be measured. I propose to formalize such things as: * set of

Re: Ignite Benchmarking Rules

Alexey, I completely agree. However, for the benchmarks to be useful, then need to be run on the same hardware all the time. Apache Ignite does not have servers sitting around, available to run the benchmarks. Would be nice to see how other projects address it. Can Amazon donate servers for the

Re: [VOTE] Apache Ignite 2.2.0 RC1

Igniters... at this point this is becoming almost amusing to watch. All we aimed to do is fix one issue with memory consumption, then bunch of community members started pouring in other fixes into this "emergency" release, and as a result, nothing works. I propose to go back to the original goal

Re: Ignite.NET static analysis with NDepend

Pavel, nice blog! If there is a way to integrate nDepend into Ignite builds, would be nice. D. On Thu, Sep 14, 2017 at 6:38 AM, Pavel Tupitsyn wrote: > Igniters, > > NDepend [1] has contacted me and provided us with build machine licenses > for their tool. > I've played

Re: ContinuousQueryWithTransformer implementation questions - 2

Hello, Vova. Can you, please, share your knowledge: Why we have abandon ContinuousQuery? Guys. I'm new in the project so can someone more experienced tell me: What's is wrong with the current implementation of ContinuousQuery? 1. initialQuery is useless - OK, understood. What else is

[GitHub] ignite pull request #2667: WIP

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2667 WIP You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5896-premerge Alternatively you can review and apply

[GitHub] ignite pull request #2662: IGNITE-6258 .NET: Thin client: Define metadata ex...

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

[GitHub] ignite pull request #2667: WIP

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

Re: Static code analysis for Java

Hm... LGTM tool looks nice! Check out all the errors it already found in Ignite :) https://lgtm.com/projects/g/apache/ignite/alerts/?mode=list=error D. On Thu, Sep 14, 2017 at 9:21 AM, Pavel Tupitsyn wrote: > Yes, we can run IDEA inspections, and this is the simplest

Re: [Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

Great news, Roman! Please share some photos and give us a short report of the conference afterward if you get a chance. Tom > On Sep 14, 2017, at 5:24 PM, Denis Magda wrote: > > Good luck, Roman! > > Community please help to spread the word! > > — > Denis > >> On

Re: [Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

Good luck, Roman! Community please help to spread the word! — Denis > On Sep 13, 2017, at 6:11 PM, Roman Shtykh wrote: > > Hi, > > I will be making a short presentation at Data Platform Conference Tokyo 2017 > on Apache Ignite with emphasis on IoT. > Attending is

Re: Ignite.NET static analysis with NDepend

That’s a useful addition! Please help to brag about: https://twitter.com/denismagda/status/908459060155912192 Prachi, would you mind adding Pavel’s blog to the blogs feed? https://ignite.apache.org/blogs.html

Re: [VOTE] Apache Ignite 2.2.0 RC1

Vladimir, Thanks for looking into this. The workaround blows out my mind :) Anyway, would you mind documenting? You’ll be able to explain it better than me. — Denis > On Sep 14, 2017, at 1:05 AM, Vladimir Ozerov wrote: > > Denis, > > As far as DML, I debugged the

Re: ContinuousQueryWithTransformer implementation questions - 2

Vladimir, If the API is so bad then it might take much more time to make up and roll out the new. Plus, there should be a community member who is ready to take it over. My suggestion would be to accept this contribution and initiate an activity towards the new API if you like. Personally, I

Re: Expiry policy for Cache.invoke

Denis, This looks like a bug. In my understanding, getExpiryForAccess should be called for any update, plus one of getExpiryForCreation/getExpiryForUpdate depending on whether it's a new entry or not. And this definitely should not depend on cache mode. -Val On Thu, Sep 14, 2017 at 3:02 AM,