IMHO it makes sense to have utility classes like this, which are likely to be useful to a variety of Hyracks applications, located in Hyracks itself. The overhead of having a separate utility package in a separate git repository is too high.
Now that Asterix and Hyracks are in the same git repo anyway, there really is no need to split this out. Just ensure that it's part of one of the hyracks deliverables. Ceej aka Chris Hillery On Sun, Apr 17, 2016 at 5:24 PM, Preston Carman <[email protected]> wrote: > A TaggedValuePointable class defines a way of accessing tagged data. A byte > is used to represent the type of data which is followed by the data. The > class is used by both AsterixDB and VXQuery. The question is where should > this shared class live? > > Currently, both AsterixDB and VXQuery build upon Hyracks. While Hyracks is > data agnostic, it does define primitive data pointables (int, long, UTF8, > etc..). Does it make sense to include a A TaggedValuePointable class with > these Hryacks pointables or put it in a new shared location? Or does this > need to be in both VXQuery and AsterixDB as separate classes. > > Thoughts? >
