Re: [IGNITE-2323] Improvments for http client

Hi Chandresh, >From what I see that task is planned to be done as a part of NodeJS integration. Andrey Gura and Sam Boikov should be working on that integration. Andrey, Sam, can you provide more details in the ticket so that Chandresh can start working on it? -- Denis On Sat, May 14, 2016 at

[GitHub] ignite pull request: IGNITE-1248 Add a method to retrieve Spring a...

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

[GitHub] ignite pull request: IGNITE-1102 - IgniteSpringBean should have ge...

Github user samaitra closed the pull request at: https://github.com/apache/ignite/pull/628 --- 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-2323] Improvments for http client

Hi Igniters, I know you all busy with your respective work. But can anyone help me out with this ticket? There aren't much information on JIRA. Thanks On Wed, May 11, 2016 at 12:52 PM, chandresh pancholi < chandreshpancholi...@gmail.com> wrote: > Hi Dmitriy, > > I have assigned it already to

Re: Ignite Release Schedules - a suggestion

How will it look branch-wise? Currently, if a feature passes a review, it ends up in master, together with bug fixes. If we were to separate bug fixes from features, then we need a different branching structure. For example, we may have another release branch which will get cherry-picked bug

Re: Introduction and Contribution Help

Hi Myles, I need to add you to the list of Jira contributors. Can you tell me your Jira username? D. On Fri, May 13, 2016 at 10:17 AM, Myles Baker wrote: > Good afternoon Dmitriy, > > Thank you for the warm welcome. I should be able to knock out this issue > and

Re: Introduction and Contribution Help

Good afternoon Dmitriy, Thank you for the warm welcome. I should be able to knock out this issue and send you a PR by the end of the day (or maybe the weekend). I cannot assign this issue to myself in JIRA yet. Should I just worry about that after I’ve implemented the fix? Thanks, Myles >

Re: Code merge in 1.6 branch at 16-th

I also have whole feature (web-console) not merged yet to ignite-1.6. Also need some review before merge. On Fri, May 13, 2016 at 10:13 PM, Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: > Anton V., is it still be possible to merge changes to 1.6 branch at Monday > 16-th? I have a

Re: Integration with Apache Apex

Hi Vladisav, Great, thanks for taking this up. Please contact us on the Apex users or dev list if you have any questions regarding the Apex side of things: http://apex.apache.org/community.html You can also create a subtask here: https://issues.apache.org/jira/browse/APEXMALHAR-2091 Thanks,

Re: Halfway to Ignite 1.6

Igniters, We postponed code freeze till monday UTC 19-00. On Thu, May 12, 2016 at 1:48 PM, Anton Vinogradov wrote: > 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

Re: Code merge in 1.6 branch at 16-th

Seems we postpone code freeze till monday UTC 19-00. So, feel free to merge changes on Monday On Fri, May 13, 2016 at 6:19 PM, Alexey Kuznetsov wrote: > I also have whole feature (web-console) not merged yet to ignite-1.6. Also > need some review before merge. > > > >

Re: Code merge in 1.6 branch at 16-th

On Fri, May 13, 2016 at 8:19 AM, Alexey Kuznetsov wrote: > I also have whole feature (web-console) not merged yet to ignite-1.6. Also > need some review before merge. > I think web-console is not affecting the main build and can be merged at any time. > > > > On Fri,

[jira] [Created] (IGNITE-3135) Old value is null in EVT_CACHE_ENTRY_EVICTED events in OFFHEAP_VALUES mode

Alexei Scherbakov created IGNITE-3135: - Summary: Old value is null in EVT_CACHE_ENTRY_EVICTED events in OFFHEAP_VALUES mode Key: IGNITE-3135 URL: https://issues.apache.org/jira/browse/IGNITE-3135

Code merge in 1.6 branch at 16-th

Anton V., is it still be possible to merge changes to 1.6 branch at Monday 16-th? I have a fix that waiting for review and it would be nice to add it in that release (IGNITE-3087 ). Thanks! Dmitry.

[jira] [Created] (IGNITE-3134) Unexpected EVT_CACHE_ENTRY_EVICTED events in OFFHEAP_TIERED mode

Alexei Scherbakov created IGNITE-3134: - Summary: Unexpected EVT_CACHE_ENTRY_EVICTED events in OFFHEAP_TIERED mode Key: IGNITE-3134 URL: https://issues.apache.org/jira/browse/IGNITE-3134 Project:

[GitHub] ignite pull request: IGNITE-2667

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/718 IGNITE-2667 Allow to start caches in PRIVATE and ISOLATED deployment modes when BinaryMarshaller is used You can merge this pull request into a Git repository by running: $ git pull

HDFS CacheStore

Hello folks - reloading on the topic to add a HDFS CacheStore module, is anybody interested in brainstorming upon the idea? I want to be consistent and make sure I capture most of the ideas, opinions and options before proceeding brute force :). As long as HDFS paradigm is append-only, maybe a

[GitHub] ignite pull request: 7.5.22

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

[jira] [Created] (IGNITE-3133) Unable to get a reference to a cache inside TX on a node that is filtered out by a node filter

Denis Magda created IGNITE-3133: --- Summary: Unable to get a reference to a cache inside TX on a node that is filtered out by a node filter Key: IGNITE-3133 URL: https://issues.apache.org/jira/browse/IGNITE-3133

Re: Ignite 1.6 release timelines

I've finished with IGNITE-2959 Ignite JTA and WebSphere Application Server 8.5.5 and has been merged to 1.6. Also, I'm going to finish the following issues before 1.6 relase (they all almost done/under review/waiting for TC): [1] IGNITE-3056

[jira] [Created] (IGNITE-3132) Distributed SQL query hangs if rebalanceMode=NONE

Alexei Scherbakov created IGNITE-3132: - Summary: Distributed SQL query hangs if rebalanceMode=NONE Key: IGNITE-3132 URL: https://issues.apache.org/jira/browse/IGNITE-3132 Project: Ignite

[GitHub] ignite pull request: IGNITE-2708

Github user ryanzz closed the pull request at: https://github.com/apache/ignite/pull/544 --- 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: Integration with Apache Apex

This will be great. Feel free to assign the ticket to yourself. On Fri, May 13, 2016 at 12:35 AM, Vladisav Jelisavcic wrote: > Hi, > > it looks really interesting to me, > I'll be glad to pick this one. > > > Best regards, > Vladisav > > > On Fri, May 13, 2016 at 7:41 AM,

Re: Integration with Apache Apex

Hi, it looks really interesting to me, I'll be glad to pick this one. Best regards, Vladisav On Fri, May 13, 2016 at 7:41 AM, Thomas Weise wrote: > Dear Ignite community, > > Apache Apex is a data in-motion processing platform. It was developed since > 2012 and recently

[GitHub] ignite pull request: 'key' is a reserved keyword in mysql and need...

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

[GitHub] ignite pull request: ignite-2982

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

[GitHub] ignite pull request: 7.5.21

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

[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