You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by 李玉...@163,
18...@163.com on 2017/02/14 12:20:14 UTC
Re: IGNITE-3727： why did not merge into the 1.8 version?
Semen,
Can this issue be merged into version 1.9?
\u5728 2016/12/13 16:18, Semyon Boikov \u5199\u9053:
> Hi,
>
> We had a lot of more priority issues so I somehow missed IGNITE-3732. As a
> workaround it is possible to create special thread pool and when message is
> sent to local node execute message listener there instead of
> IgniteMessaging usage.
>
> Thanks
>
> On Sun, Dec 11, 2016 at 5:56 AM, Denis Magda <dm...@apache.org> wrote:
>
>> Alright, looks like I confused it with some other task initially.
>>
>> The ticket you\u2019re talking about is still under review and looks abandoned
>> https://issues.apache.org/jira/browse/IGNITE-3727 <
>> https://issues.apache.org/jira/browse/IGNITE-3727>
>>
>> Dmitriy G., Sam, is the ticket ready for the merge?
>>
>> \u2014
>> Denis
>>
>>> On Dec 10, 2016, at 6:29 PM, \u674e\u7389\u73cf@163 <18...@163.com> wrote:
>>>
>>> Denis\uff0c
>>>
>>> I found the branch 3727:
>>>
>>> https://github.com/gridgain/apache-ignite/tree/ignite-3727-2
>>>
>>> But it appear that the code is not merged into the master?
>>>
>>> for example, IgniteMessagingImpl.java,the related code is still an old
>> version,8 months ago.
>>>
>>> \u5728 2016/12/10 22:56, Denis Magda \u5199\u9053:
>>>> Hi,
>>>>
>>>> It was released in 1.8. I\u2019ve just checked git logs.
>>>>
>>>> How did you come up with such a conclusion? Something doesn't work on
>> your side?
>>>> \u2014
>>>> Denis
>>>>
>>>>> On Dec 10, 2016, at 5:39 AM, \u674e\u7389\u73cf@163 <18...@163.com> wrote:
>>>>>
>>>>> Hi\uff1a
>>>>>
>>>>>
>>>>> IGNITE-3727,this issue has been fixed and tested in september\uff0cwhy did
>> not merge into the 1.8 version?
>>>>>
>>
Re: IGNITE-3727： why did not merge into the 1.8 version?
Posted by Semyon Boikov <sb...@gridgain.com>.
OK, I'll try to review/merge it today.
Thanks!
On Tue, Feb 14, 2017 at 3:20 PM, 李玉珏@163 <18...@163.com> wrote:
> Semen,
>
>
> Can this issue be merged into version 1.9?
>
>
> 在 2016/12/13 16:18, Semyon Boikov 写道:
>
>> Hi,
>>
>> We had a lot of more priority issues so I somehow missed IGNITE-3732. As a
>> workaround it is possible to create special thread pool and when message
>> is
>> sent to local node execute message listener there instead of
>> IgniteMessaging usage.
>>
>> Thanks
>>
>> On Sun, Dec 11, 2016 at 5:56 AM, Denis Magda <dm...@apache.org> wrote:
>>
>> Alright, looks like I confused it with some other task initially.
>>>
>>> The ticket you’re talking about is still under review and looks abandoned
>>> https://issues.apache.org/jira/browse/IGNITE-3727 <
>>> https://issues.apache.org/jira/browse/IGNITE-3727>
>>>
>>> Dmitriy G., Sam, is the ticket ready for the merge?
>>>
>>> —
>>> Denis
>>>
>>> On Dec 10, 2016, at 6:29 PM, 李玉珏@163 <18...@163.com> wrote:
>>>>
>>>> Denis，
>>>>
>>>> I found the branch 3727:
>>>>
>>>> https://github.com/gridgain/apache-ignite/tree/ignite-3727-2
>>>>
>>>> But it appear that the code is not merged into the master?
>>>>
>>>> for example, IgniteMessagingImpl.java,the related code is still an old
>>>>
>>> version,8 months ago.
>>>
>>>>
>>>> 在 2016/12/10 22:56, Denis Magda 写道:
>>>>
>>>>> Hi,
>>>>>
>>>>> It was released in 1.8. I’ve just checked git logs.
>>>>>
>>>>> How did you come up with such a conclusion? Something doesn't work on
>>>>>
>>>> your side?
>>>
>>>> —
>>>>> Denis
>>>>>
>>>>> On Dec 10, 2016, at 5:39 AM, 李玉珏@163 <18...@163.com> wrote:
>>>>>>
>>>>>> Hi：
>>>>>>
>>>>>>
>>>>>> IGNITE-3727,this issue has been fixed and tested in september，why did
>>>>>>
>>>>> not merge into the 1.8 version?
>>>
>>>>
>>>>>>
>>>
>
>