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 <[email protected]> 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 <[email protected]> wrote: > > @Ildar: +1 > > > > Best, > > Taewoo > > > > On Wed, May 31, 2017 at 11:57 AM, Ildar Absalyamov < > > [email protected]> 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 <[email protected]> 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 > >> > >> >
