[GitHub] ignite pull request: Improved JDBC error handling by consistent us...

GitHub user krosenvold opened a pull request: https://github.com/apache/ignite/pull/705 Improved JDBC error handling by consistent usage of jdk7 try-with res… …ources You can merge this pull request into a Git repository by running: $ git pull https://github.com/krosenvold/

[GitHub] ignite pull request: IGNITE-3112 .NET: Allow merging Spring XML co...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/706 IGNITE-3112 .NET: Allow merging Spring XML config with .NET config You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-311

[jira] [Created] (IGNITE-3116) Cancel force key futures when node stops

Semen Boikov created IGNITE-3116: Summary: Cancel force key futures when node stops Key: IGNITE-3116 URL: https://issues.apache.org/jira/browse/IGNITE-3116 Project: Ignite Issue Type: Bug

Re: Ignite 1.6 release timelines

Hi, there is one more .NET ticket to be merged to 1.6: IGNITE-3112 .NET: Allow merging Spring XML config with .NET config Other two 1.6 .NET tickets are documentation-related and have no code changes: IGNITE-2963, IGNITE-3101 Thanks, Pavel On Wed, May 11, 2016 at 10:03 PM, Andrey Gura wrote: >

[GitHub] ignite pull request: ignite-3116

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

[GitHub] ignite pull request: 7.5.20

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

Re: Ignite 1.6 release timelines

I merged into 1.6 one more ticket: IGNITE-2919 Implemented script execution when alert triggered. https://issues.apache.org/jira/browse/IGNITE-2919 On Thu, May 12, 2016 at 3:29 PM, Pavel Tupitsyn wrote: > Hi, there is one more .NET ticket to be merged to 1.6: > IGNITE-3112 .NET: Allow merging Sp

ignite-3023 merged

jcfiorenzano, thank you for contributing fix for ignite-3023 Rename keyBackups to Backups for performance advices printed out on a node ( https://issues.apache.org/jira/browse/IGNITE-3023). I merged it to master. Please close the PR. --Yakov

[jira] [Created] (IGNITE-3117) Weblogic manual tests for HttpSession caching.

Dmitry Karachentsev created IGNITE-3117: --- Summary: Weblogic manual tests for HttpSession caching. Key: IGNITE-3117 URL: https://issues.apache.org/jira/browse/IGNITE-3117 Project: Ignite

Re: Ignite 1.6 release timelines

Yakov, Processed all the tickets mentioned in 1. The only one is left is the following https://issues.apache.org/jira/browse/IGNITE-2954 Alex G. I do remember you’ve fixed IGNITE-2954 before. Have you merged it into the master? Is the fix in i

visorcmd alerts: improvements and fixes

Hello Igniters. I implement execution of custom script on alert for visorcmd: https://issues.apache.org/jira/browse/IGNITE-2919. Now some logic can be defined in case of specific grid conditions in format sh/bat file. Also fixed reaction on alert condition switch: https://issues.apache.org/jira/b

[jira] [Created] (IGNITE-3118) .NET: CacheConfiguration.EvictionPolicy

Pavel Tupitsyn created IGNITE-3118: -- Summary: .NET: CacheConfiguration.EvictionPolicy Key: IGNITE-3118 URL: https://issues.apache.org/jira/browse/IGNITE-3118 Project: Ignite Issue Type: Impr

[GitHub] ignite pull request: 7.5.20

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

[GitHub] ignite pull request: 7.5.20

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

[GitHub] ignite pull request: IGNITE-3118 .NET: CacheConfiguration.Eviction...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/710 IGNITE-3118 .NET: CacheConfiguration.EvictionPolicy You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3118 Alternativel

Re: Halfway to Ignite 1.6

Igniters, Ignite 1.6 almost ready to be finally tested. Branch ignite-1.6 now contains all changes scheduled for 1.6. In case you want to add something else to this release, please note that pushes to ignite-1.6 allowed till Friday (Aug 13) 19:00 UTC. After that date only fixes will allowed. On

Re: Halfway to Ignite 1.6

Typo fix: Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00 UTC. On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov wrote: > Igniters, > > Ignite 1.6 almost ready to be finally tested. > > Branch ignite-1.6 now contains all changes scheduled for 1.6. > > In case you want to add some

Re: Ignite 1.6 release timelines

And one more .NET ticket: IGNITE-3118 .NET: CacheConfiguration.EvictionPolicy On Thu, May 12, 2016 at 12:20 PM, Denis Magda wrote: > Yakov, > > Processed all the tickets mentioned in 1. The only one is left is the > following > https://issues.apache.org/jira/browse/IGNITE-2954 < > https://issues

[jira] [Created] (IGNITE-3119) NuGet

Pavel Tupitsyn created IGNITE-3119: -- Summary: NuGet Key: IGNITE-3119 URL: https://issues.apache.org/jira/browse/IGNITE-3119 Project: Ignite Issue Type: Sub-task Reporter: Pavel T

[jira] [Created] (IGNITE-3120) LINQ Provider

Pavel Tupitsyn created IGNITE-3120: -- Summary: LINQ Provider Key: IGNITE-3120 URL: https://issues.apache.org/jira/browse/IGNITE-3120 Project: Ignite Issue Type: Sub-task Reporter:

[jira] [Created] (IGNITE-3121) Atomics

Pavel Tupitsyn created IGNITE-3121: -- Summary: Atomics Key: IGNITE-3121 URL: https://issues.apache.org/jira/browse/IGNITE-3121 Project: Ignite Issue Type: Sub-task Reporter: Pavel

[jira] [Created] (IGNITE-3122) Cluster Configuration

Pavel Tupitsyn created IGNITE-3122: -- Summary: Cluster Configuration Key: IGNITE-3122 URL: https://issues.apache.org/jira/browse/IGNITE-3122 Project: Ignite Issue Type: Sub-task R

[jira] [Created] (IGNITE-3123) Network Configuration

Pavel Tupitsyn created IGNITE-3123: -- Summary: Network Configuration Key: IGNITE-3123 URL: https://issues.apache.org/jira/browse/IGNITE-3123 Project: Ignite Issue Type: Sub-task R

[jira] [Created] (IGNITE-3124) Cache Modes

Pavel Tupitsyn created IGNITE-3124: -- Summary: Cache Modes Key: IGNITE-3124 URL: https://issues.apache.org/jira/browse/IGNITE-3124 Project: Ignite Issue Type: Sub-task Reporter: P

[jira] [Created] (IGNITE-3125) Query Configuration

Pavel Tupitsyn created IGNITE-3125: -- Summary: Query Configuration Key: IGNITE-3125 URL: https://issues.apache.org/jira/browse/IGNITE-3125 Project: Ignite Issue Type: Sub-task Rep

[jira] [Created] (IGNITE-3127) Store Configuration

Pavel Tupitsyn created IGNITE-3127: -- Summary: Store Configuration Key: IGNITE-3127 URL: https://issues.apache.org/jira/browse/IGNITE-3127 Project: Ignite Issue Type: Sub-task Rep

[jira] [Created] (IGNITE-3126) Transaction Configuration

Pavel Tupitsyn created IGNITE-3126: -- Summary: Transaction Configuration Key: IGNITE-3126 URL: https://issues.apache.org/jira/browse/IGNITE-3126 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-3128) Expiry Policy Configuration

Pavel Tupitsyn created IGNITE-3128: -- Summary: Expiry Policy Configuration Key: IGNITE-3128 URL: https://issues.apache.org/jira/browse/IGNITE-3128 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-3129) All config samples should contain C#, app.config and Spring XML tabs

Pavel Tupitsyn created IGNITE-3129: -- Summary: All config samples should contain C#, app.config and Spring XML tabs Key: IGNITE-3129 URL: https://issues.apache.org/jira/browse/IGNITE-3129 Project: Ign

[GitHub] ignite pull request: IGNITE-3113: C++ documentation improvements.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/711 IGNITE-3113: C++ documentation improvements. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-3113 Alternatively you can r

[jira] [Created] (IGNITE-3130) .NET: TcpDiscoverySpi missing properties

Pavel Tupitsyn created IGNITE-3130: -- Summary: .NET: TcpDiscoverySpi missing properties Key: IGNITE-3130 URL: https://issues.apache.org/jira/browse/IGNITE-3130 Project: Ignite Issue Type: Imp

Re: Ignite 1.6 release timelines

There is one more C++ ticket I'd like to be included in 1.6 - IGNITE-3113 [1]. [1] - https://issues.apache.org/jira/browse/IGNITE-3113 Best Regards, Igor On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn wrote: > And one more .NET ticket: IGNITE-3118 .NET: > CacheConfiguration.EvictionPolicy > >

[GitHub] ignite pull request: IGNITE-3090 Memory leak in IgniteH2Indexing p...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/712 IGNITE-3090 Memory leak in IgniteH2Indexing prepared statements cache… Add cleanupStmtCache method that is called periodically by the GridTimeoutProcessor. Add memory leaks unit test

[GitHub] ignite pull request: ignite-2382 JDBC drivers improvements

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/713 ignite-2382 JDBC drivers improvements You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2382 Alternatively you can re

Re: Ignite 1.6 release timelines

I'm going to merge Ignite Web Console into ignite-1.6 https://issues.apache.org/jira/browse/IGNITE-843 On Thu, May 12, 2016 at 9:30 PM, Igor Sapego wrote: > There is one more C++ ticket I'd like to be included in 1.6 - IGNITE-3113 > [1]. > > [1] - https://issues.apache.org/jira/browse/IGNITE-31

Re: Ignite 1.6 release timelines

Also I already implemented "CacheJdbcPojoStoreFactory.dataSource property should be replaced with Factory" https://issues.apache.org/jira/browse/IGNITE-2832 And I think it will be cool to merge into ignite-1.6 But I need a review. Val, could you take a look? You may compare branch ignite-2832 wit

[GitHub] ignite pull request: IGNITE-3115: ODBC-related minor fixes.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/714 IGNITE-3115: ODBC-related minor fixes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-3115 Alternatively you can review

[GitHub] ignite pull request: IGNITE-3130 .NET: TcpDiscoverySpi missing pro...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/715 IGNITE-3130 .NET: TcpDiscoverySpi missing properties You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3130 Alternative

Re: Ignite 1.6 release timelines

On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov wrote: > Also I already implemented "CacheJdbcPojoStoreFactory.dataSource property > should be replaced with Factory" > https://issues.apache.org/jira/browse/IGNITE-2832 > > And I think it will be cool to merge into ignite-1.6 > But I need a revie

IGNITE-1192 in progress

Hello everybody, I have assigned to me the issue IGNITE-1192, this issues is about the integration about Ignite and Spring Data, I am going to begin to research how do that, so any advice or idea will be welcome. Thanks in advance

Re: IGNITE-1192 in progress

Thanks Juan. I am not a Spring Data expert, but would be curious to see what you can dig out, if you don’t mind sharing your findings here. D. On Thu, May 12, 2016 at 7:48 PM, Juan Carlos Fiorenzano < jcfiorenzan...@gmail.com> wrote: > Hello everybody, I have assigned to me the issue IGNITE-119

Re: IGNITE-1192 in progress

don't worry I'm going to share every advance with the community On Thu, May 12, 2016 at 10:51 PM, Dmitriy Setrakyan wrote: > Thanks Juan. > > I am not a Spring Data expert, but would be curious to see what you can dig > out, if you don’t mind sharing your findings here. > > D. > > On Thu, May 12

Re: visorcmd alerts: improvements and fixes

Thanks Vasily! The custom alert logic is a great addition. Do we need to add documentation for it? On Thu, May 12, 2016 at 2:30 AM, Vasiliy Sisko wrote: > Hello Igniters. > > I implement execution of custom script on alert for visorcmd: > https://issues.apache.org/jira/browse/IGNITE-2919. Now so

Re: Introduction and Contribution Help

Hi Myles, Welcome to the Ignite community! How about this ticket? Looks like it could be a good entry point one: https://issues.apache.org/jira/browse/IGNITE-1794 D. On Wed, May 11, 2016 at 6:58 AM, Myles Baker wrote: > Hi all, > > I just wanted to introduce myself - I am interested in Ignite

[jira] [Created] (IGNITE-3131) Connectors for Apache Apex

Dmitriy Setrakyan created IGNITE-3131: - Summary: Connectors for Apache Apex Key: IGNITE-3131 URL: https://issues.apache.org/jira/browse/IGNITE-3131 Project: Ignite Issue Type: Improvement

Integration with Apache Apex

Dear Ignite community, Apache Apex is a data in-motion processing platform. It was developed since 2012 and recently became an ASF top level project: http://apex.apache.org/docs.html The Apex engine can process large scale, high throughput streams with very low latency. It is a stateful system w

[GitHub] ignite pull request: IGNITE-2954 - Added tests for various read-th...

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