[jira] [Created] (IGNITE-3821) Web console: exception on clicking Showquery after scan

Pavel Konstantinov created IGNITE-3821: -- Summary: Web console: exception on clicking Showquery after scan Key: IGNITE-3821 URL: https://issues.apache.org/jira/browse/IGNITE-3821 Project: Ignite

[jira] [Created] (IGNITE-3820) Web console: 'undo' apper in wrong section

Pavel Konstantinov created IGNITE-3820: -- Summary: Web console: 'undo' apper in wrong section Key: IGNITE-3820 URL: https://issues.apache.org/jira/browse/IGNITE-3820 Project: Ignite

Re: Pull request for IGNITE-3699

Hi Amir, I reviewed your changes and left my comments in the ticket. -Val On Wed, Aug 31, 2016 at 8:17 AM, Amir Akhmedov wrote: > Hi community, > > I raised a pull request [1] Can you please review it? > > [1] https://github.com/apache/ignite/pull/1011 > > Thanks. >

[GitHub] ignite pull request #1024: IGNITE-3819: Added prints for ODBC errors.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1024 IGNITE-3819: Added prints for ODBC errors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3819 Alternatively

IGNITE-3601 Read-only optimistic transaction shouldn't throw an exception if entry version was not changed.

Hi, I prepared PR[1] for read only transaction. [1]: https://github.com/apache/ignite/pull/1001

[jira] [Created] (IGNITE-3819) ODBC: Print stack trace on error.

Igor Sapego created IGNITE-3819: --- Summary: ODBC: Print stack trace on error. Key: IGNITE-3819 URL: https://issues.apache.org/jira/browse/IGNITE-3819 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1023: IGNITE-3613 IGFS: IgfsImpl.size() doesn't take se...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1023 IGNITE-3613 IGFS: IgfsImpl.size() doesn't take secondary file system in count. You can merge this pull request into a Git repository by running: $ git pull

IGNITE-532 Implement IgniteAkkaStreamer to stream data from Akka actors.

Hi, I have raised PR[1] for JIRA tickets[2]. Please review and let me know if any changes required. [1] https://github.com/apache/ignite/pull/1019 [2]https://issues.apache.org/jira/browse/IGNITE-532 -- Chandresh Pancholi Senior Software Engineer Flipkart.com

[GitHub] ignite pull request #1019: IGNITE-532 - Implement IgniteAkkaStreamer to stre...

GitHub user chandresh-pancholi opened a pull request: https://github.com/apache/ignite/pull/1019 IGNITE-532 - Implement IgniteAkkaStreamer to stream data from Akka actors You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1018: Ignite 3817

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

[GitHub] ignite pull request #1017: IGNITE-3809: Fix for ArrayIndexOutOfBoundsExcepti...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/1017 IGNITE-3809: Fix for ArrayIndexOutOfBoundsException in GridUnsafeLru. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite

[GitHub] ignite pull request #997: IGNITE-3789 Test for EntryProcessor/partition evts

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

Re: IGNITE-1192 Implementation (Integration with Spring Data)

Greetings, guys. So, the current implementation was found adequate for the first version. But there are two issues which Semen found. 1) now cache name is bound to a repository at compile time, could you please try to investigate if a more flexible binding is possible? 2) as I see now all

[jira] [Created] (IGNITE-3816) CacheJdbcPojoStore check for column names should be case insensitive

Alexey Kuznetsov created IGNITE-3816: Summary: CacheJdbcPojoStore check for column names should be case insensitive Key: IGNITE-3816 URL: https://issues.apache.org/jira/browse/IGNITE-3816

new committer: Saikat Maitra

The Project Management Committee (PMC) for Apache Ignite has asked Saikat Maitra to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should