[GitHub] ignite pull request: ignite-2751

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

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

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

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

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

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

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

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

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

[jira] [Created] (IGNITE-3145) Display in metadata list cache schema name instead of cache name if schema present in cache configuration

Pavel Konstantinov created IGNITE-3145: -- Summary: Display in metadata list cache schema name instead of cache name if schema present in cache configuration Key: IGNITE-3145 URL: https://issues.apache.org/jir

Fwd: Eviction Events with offheap values

Guys, Resending this question to the dev list. Doesn’t Ignite fire an eviction event whenever an entry is evicted from off-heap memory? D. -- Forwarded message -- From: Alexei Scherbakov Date: Mon, May 16, 2016 at 1:33 AM Subject: Re: Eviction Events with offheap values To: u...

Re: Doubts

Hi Juan Carlos, If you are interested in contributing, you can find some tickets to get started with here: https://ignite.apache.org/community/contribute.html#pick-ticket This should make the learning curve to start out with Ignite development easier. If you have any questions, please send them

Re: Halfway to Ignite 1.6

I will be presenting at IMC Summit next week in Bay Area, and it sure would be nice to talk about 1.6 release and the new features. Would be great if we could send it for vote on Wednesday morning. This would give a chance for the vote to pass by EOD on Friday, if everything is OK. D. On Mon, May

Re: Ignite 1.6 release timelines

https://issues.apache.org/jira/browse/IGNITE-2832 "CacheJdbcPojoStoreFactory.dataSource property should be replaced with Factory" Reviewed by Semen and merged into ignite-1.6 On Mon, May 16, 2016 at 10:56 PM, Igor Sapego wrote: > Hi, here is a list of major C++ features included in 1.6: > > * O

Re: Ignite 1.6 release timelines

Hi, here is a list of major C++ features included in 1.6: * ODBC driver for Ignite (IGNITE-1786) * Transactions API for CPP client (IGNITE-2805) * Simplified Autotools build process (IGNITE-2823) * Date and Timestamp types implementation (IGNITE-) Best Regards, Igor On Fri, May 13, 2016 at 4

Re: Halfway to Ignite 1.6

Guys I'm concerned that we postpone once again the date of code freeze. It shifts dates of testing and release and it seems we won't be able to send to voting this week On Mon, May 16, 2016 at 5:43 PM, Anton Vinogradov wrote: > Thanks everyone for checking! > > Only 8 tickets left! > > Seems co

Re: Halfway to Ignite 1.6

Thanks everyone for checking! Only 8 tickets left! Seems contributors still need 1-2 days to pass codereview and merge final changes. We postponed code freeze till Wednesday UTC 19-00. Hope, this will be the last time. On Mon, May 16, 2016 at 3:56 PM, Anton Vinogradov wrote: > Igniters, > > We

[GitHub] ignite pull request: IGNITE-3140: Added test for UTF-8 string form...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/723 IGNITE-3140: Added test for UTF-8 string format validity. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-3140 Alternativ

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

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

[GitHub] ignite pull request: Fix race condition on dynamic cache creation

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/697 --- 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 featu

Re: Halfway to Ignite 1.6

Igniters, We still have 32 issues with status "In Progress" or "Patch Available" and fixVersion = 1.6. Full list

Re: Deadlock detection usage

Hi, There is no example how to use it. It just works :) For now deadlock detection supported only by pessimistic transactions with timeout. Near cache isn't supported. User should just start some pessimistic transactions with timeout and if timeout expired then deadlock detection will try to fin

[jira] [Created] (IGNITE-3144) Refactor Schema Import Utility. Split for two modules: schema-import and schema-import-db

Alexey Kuznetsov created IGNITE-3144: Summary: Refactor Schema Import Utility. Split for two modules: schema-import and schema-import-db Key: IGNITE-3144 URL: https://issues.apache.org/jira/browse/IGNITE-3144

[GitHub] ignite pull request: Test execute Visor tasks via REST HTTP

Github user akuznetsov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/720 --- 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 fe

[jira] [Created] (IGNITE-3143) Implement support for executing Visor tasks via REST HTTP

Alexey Kuznetsov created IGNITE-3143: Summary: Implement support for executing Visor tasks via REST HTTP Key: IGNITE-3143 URL: https://issues.apache.org/jira/browse/IGNITE-3143 Project: Ignite

RE: 1.5.0.final is breaking packaging: osgi dependency is non-existent

I'd love to elaborate, Konstantin, but I can't. I have no experience with the package management tools, neither yum nor rpm. BTW, those Spring dependencies are optional, as far as I know. They are only required if Spring framework is used by the application (Spring XML configuration, for exampl

[GitHub] ignite pull request: Ignite 3087 1.6 merge

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

[GitHub] ignite pull request: IGNITE-3139 .Net: UTF-16 surrogate symbols ar...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/721 IGNITE-3139 .Net: UTF-16 surrogate symbols are not serialized properly You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite

[jira] [Created] (IGNITE-3142) Do not send event when primary node has left grid.

Vladislav Pyatkov created IGNITE-3142: - Summary: Do not send event when primary node has left grid. Key: IGNITE-3142 URL: https://issues.apache.org/jira/browse/IGNITE-3142 Project: Ignite

Re: Doubts

Juan Carlos, First of all you should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute DataG

[jira] [Created] (IGNITE-3141) IgnitePartitionedLockSelfTest fails on TC

Semen Boikov created IGNITE-3141: Summary: IgnitePartitionedLockSelfTest fails on TC Key: IGNITE-3141 URL: https://issues.apache.org/jira/browse/IGNITE-3141 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3140) C++: UTF-16 surrogate symbols are not serialized properly

Denis Magda created IGNITE-3140: --- Summary: C++: UTF-16 surrogate symbols are not serialized properly Key: IGNITE-3140 URL: https://issues.apache.org/jira/browse/IGNITE-3140 Project: Ignite Issu

[jira] [Created] (IGNITE-3139) .Net: UTF-16 surrogate symbols are not serialized properly

Denis Magda created IGNITE-3139: --- Summary: .Net: UTF-16 surrogate symbols are not serialized properly Key: IGNITE-3139 URL: https://issues.apache.org/jira/browse/IGNITE-3139 Project: Ignite Iss

[jira] [Created] (IGNITE-3138) IgniteDataStreamer: failures are not shown on the streaming side

Denis Magda created IGNITE-3138: --- Summary: IgniteDataStreamer: failures are not shown on the streaming side Key: IGNITE-3138 URL: https://issues.apache.org/jira/browse/IGNITE-3138 Project: Ignite

[jira] [Created] (IGNITE-3137) IgniteDataStreamer silently hangs if exception happens on a remote side

Denis Magda created IGNITE-3137: --- Summary: IgniteDataStreamer silently hangs if exception happens on a remote side Key: IGNITE-3137 URL: https://issues.apache.org/jira/browse/IGNITE-3137 Project: Ignite

[GitHub] ignite pull request: Test execute Visor tasks via REST HTTP

GitHub user akuznetsov-gridgain opened a pull request: https://github.com/apache/ignite/pull/720 Test execute Visor tasks via REST HTTP You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-7 Alter

[GitHub] ignite pull request: ignite-3116

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