IGNITE-2377 Docker image hangs on Mac OS

I have verified on OS X Yosemite (V 10.10.5) with docker 1.12 with ignite 1.7 and it worked fine. It would be great if someone verifies it also. Thanks -- Chandresh Pancholi Senior Software Engineer Flipkart.com Email-id:chandresh.panch...@flipkart.com Contact:08951803660

Re: Ignite 2.0 tasks/roadmap

I’ve created an umbrella ticket for REST https://issues.apache.org/jira/browse/IGNITE-3879 And I wouldn’t deprecate anything until the next version gets released ;) — Denis > On Sep 9, 2016, at 6:37 AM, Sergey Kozlov wrote: > > Denis > > Ge

[jira] [Created] (IGNITE-3879) Next generation of Ignite's REST API

Denis Magda created IGNITE-3879: --- Summary: Next generation of Ignite's REST API Key: IGNITE-3879 URL: https://issues.apache.org/jira/browse/IGNITE-3879 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3878) Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent

Nikolay Tikhonov created IGNITE-3878: Summary: Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent Key: IGNITE-3878 URL: https://issues.apache.org/jira/browse/IGNITE-3878 Project: Ignit

Re: Hello

Hi Hanu, Welcome to the Ignite community! 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+

[jira] [Created] (IGNITE-3877) Clarify if IgfsFile -> FileStatus conversion should treat groupBlockSize as blockSize

Ivan Veselovsky created IGNITE-3877: --- Summary: Clarify if IgfsFile -> FileStatus conversion should treat groupBlockSize as blockSize Key: IGNITE-3877 URL: https://issues.apache.org/jira/browse/IGNITE-3877

[jira] [Created] (IGNITE-3876) ODBC: Check all output parameters for nulls before assignment.

Igor Sapego created IGNITE-3876: --- Summary: ODBC: Check all output parameters for nulls before assignment. Key: IGNITE-3876 URL: https://issues.apache.org/jira/browse/IGNITE-3876 Project: Ignite

Re: Ignite 2.0 tasks/roadmap

Denis Generally I'm fine for your approach. I think for 2.0 (or may be for a next 1.x minor version) we can note that currently REST API is deprecated. It will allow us to replace REST by a new implementation once it will be done. On Fri, Sep 9, 2016 at 4:11 PM, Denis Magda wrote: > Sergey, > >

Re: Ignite 2.0 tasks/roadmap

Sergey, I do agree with you that Ignite’s REST API implementation has to be revisited. Your concerns sound reasonable. But personally I wouldn’t rush trying to release it under 2.0 because NodeJS won’t be a part of this release while it can propose additional requirements to the next generation

[GitHub] ignite pull request #1053: Ignite 481

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

[jira] [Created] (IGNITE-3875) Create separate thread pool for data streamer.

Vladimir Ozerov created IGNITE-3875: --- Summary: Create separate thread pool for data streamer. Key: IGNITE-3875 URL: https://issues.apache.org/jira/browse/IGNITE-3875 Project: Ignite Issue T

[jira] [Created] (IGNITE-3874) sync putIfAbsent forever blocked on all nodes after one node is stopped

Anton Vinogradov created IGNITE-3874: Summary: sync putIfAbsent forever blocked on all nodes after one node is stopped Key: IGNITE-3874 URL: https://issues.apache.org/jira/browse/IGNITE-3874 Proje

[GitHub] ignite pull request #1052: Ignite 1.5.31

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

[GitHub] ignite pull request #999: Ignite 1.5.31

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

[jira] [Created] (IGNITE-3873) ODBC: Create installer for the ODBC.

Igor Sapego created IGNITE-3873: --- Summary: ODBC: Create installer for the ODBC. Key: IGNITE-3873 URL: https://issues.apache.org/jira/browse/IGNITE-3873 Project: Ignite Issue Type: Task

Re: Ignite 2.0 tasks/roadmap

Vova, There are more issues than processing (String, String) only: we can't process JSON objects as values, current implementation doesn't follow general RESTfull API requirements. Moreover we're still have no connectors for PHP, Python and other popular languages for web development of LAMP marke

[GitHub] ignite pull request #1051: IGNITE-3868: Fix for driver installiation.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1051 IGNITE-3868: Fix for driver installiation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3868 Alternatively yo

[GitHub] ignite pull request #957: IGNITE-3665: Updated KafkaStreamer dependencies.

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

Re: Ignite 2.0 tasks/roadmap

Denis, Very good catch! Our REST API in ir is current appearance are virtually useless because it only operates on strings. We'd better to design the new one.with blackjack and etc.. On Fri, Sep 9, 2016 at 3:39 AM, Denis Magda wrote: > Basically, we can have two versions of the REST API if we w