You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "P. Taylor Goetz" <pt...@gmail.com> on 2016/09/12 19:44:00 UTC
Re: Clojure to Java Migration (was: How does Storm's OutputCollector work?)
> On Sep 12, 2016, at 3:26 PM, S G <sg...@gmail.com> wrote:
>
> Just curious, how much of the code-base is planned to be moved away from
> clojure to Java?
Ultimately all the Clojure code will move to Java. The initial focus is to get the main (i.e. non-test) code converted before migrating the unit test code.
> When do we plan to make a release for the Java-based code?
There is no specific date set, so the release will happen once the conversion is complete, blocker bugs resolved, etc. I imagine we could release before the test code is migrated.
-Taylor
>
> On Mon, Sep 12, 2016 at 6:21 AM, Bobby Evans <ev...@yahoo-inc.com.invalid>
> wrote:
>
>> Manu Zhang is correct in his answer. The main reason why you cannot find
>> a class that implements that interface is because in all released versions
>> of storm the code was written in clojure, so it is hidden away for people
>> who are used to just java. - Bobby
>>
>> On Monday, September 12, 2016 12:09 AM, Manu Zhang <
>> owenzhang1990@gmail.com> wrote:
>>
>>
>> Hi T.I.,
>>
>> Answered your question on StackOverflow. Hope that helps.
>>
>> Thanks,
>> Manu
>>
>> On Mon, Sep 12, 2016 at 11:36 AM Tech Id <te...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Can someone help provide a better understanding of Storm's
>> OutputCollector?
>>> A question for the same can be found at
>>>
>>> http://stackoverflow.com/questions/39439336/how-does-
>> storms-outputcollector-work
>>>
>>> Thanks,
>>> T.I.
>>>
>>
>>
>>
>>