asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yingyi Bu <buyin...@gmail.com>
Subject Re: Modules that could be removed?
Date Wed, 31 May 2017 23:41:19 GMT
+1.

Best,
Yingyi

On Wed, May 31, 2017 at 4:22 PM, Till Westmann <tillw@apache.org> wrote:

> I read this discussion that Ildar’s suggestion to move asterix-experiments
> to a different repo would be a solution that works for everybody.
>
> Did I read that correctly or did someone disagree with such an approach?
>
> Cheers,
> Till
>
>
> On 31 May 2017, at 16:14, Mike Carey wrote:
>
> This should be decided by more knowlegeable folks than me - it just seems
>> "weird" to me that that's in the main code base and not outside (as a super
>> useful client package).
>>
>>
>> On 5/31/17 4:12 PM, Chris Hillery wrote:
>>
>>> If we move asterix-experiments out, we would need to change the current
>>> Perf job at Couchbase. However I think the change would actually make
>>> that
>>> job less complicated, at least if that allowed one to use a pre-compiled
>>> Asterix distribution for experiments rather than requiring the full
>>> source
>>> code to be available.
>>>
>>> Ceej
>>> aka Chris Hillery
>>>
>>> On Wed, May 31, 2017 at 2:53 PM, Yingyi Bu <buyingyi@gmail.com> wrote:
>>>
>>> The code in asterix-experiments is not well organized, e.g.:
>>>>
>>>> https://github.com/apache/asterixdb/tree/master/asterixdb/
>>>> asterix-experiments/src/main/java/org/apache/asterix/experiment/builder
>>>> https://github.com/apache/asterixdb/tree/master/asterixdb/
>>>> asterix-experiments/src/main/java/org/apache/asterix/experiment/report
>>>>
>>>> Can anyone who actively uses asterix-experiments clean up the code?
>>>>
>>>> An alternative approach would be to put it in a separate github repo,
>>>> if
>>>> it is relatively independent of AsterixDB.
>>>>
>>>> Best,
>>>> Yingyi
>>>>
>>>>
>>>> On Wed, May 31, 2017 at 12:31 PM, Ian Maxon <imaxon@uci.edu> wrote:
>>>>
>>>> I also would vouch for keeping asterix-experiments in. 'asterix-tools'
>>>>> and the others could probably go.
>>>>>
>>>>> On Wed, May 31, 2017 at 11:58 AM, Taewoo Kim <wangsaeu@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> @Ildar: +1
>>>>>>
>>>>>> Best,
>>>>>> Taewoo
>>>>>>
>>>>>> On Wed, May 31, 2017 at 11:57 AM, Ildar Absalyamov <
>>>>>> ildar.absalyamov@gmail.com> wrote:
>>>>>>
>>>>>> I found Young-Seok’s asterix-experiment package useful for everyone,
>>>>>>>
>>>>>> who
>>>>
>>>>> is doing any kind of experiments.
>>>>>>> Can we instead make an ‘asterix-contrib’ repo and move it
there, the
>>>>>>>
>>>>>> same
>>>>>
>>>>>> way we did with asterix-bad?
>>>>>>> We can also launch an automated build in Jenkins to verify it
builds
>>>>>>> against master, again the same way BAD is working. This package
does
>>>>>>>
>>>>>> not
>>>>
>>>>> have a lot of dependencies, so it will be fairly painless to maintain
>>>>>>>
>>>>>> it.
>>>>>
>>>>>> On May 31, 2017, at 09:06, Yingyi Bu <buyingyi@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi dev,
>>>>>>>>
>>>>>>>>     I wonder if the following potentially obsolete modules
could be
>>>>>>>>
>>>>>>> moved
>>>>>
>>>>>> out of the AsterixDB code base:
>>>>>>>>     -- asterix-experiment
>>>>>>>>     -- asterix-tools
>>>>>>>>     -- hyracks-dist
>>>>>>>>     -- hyracks-sever
>>>>>>>>
>>>>>>>>     Any thoughts?
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Yingyi
>>>>>>>>
>>>>>>> Best regards,
>>>>>>> Ildar
>>>>>>>
>>>>>>>
>>>>>>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message