Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.incubator.apache.org
Sender: Ildar Absalyamov <ty13r.derden@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: Metadata changes
From: Ildar Absalyamov <ildar.absalyamov@gmail.com>
In-Reply-To: 
 <CAE1xAnvC0oGzvuOqkuOd+jF-Yt0pPU1WmKSKKMTJY7UxD+M7YQ@mail.gmail.com>
Date: Mon, 14 Dec 2015 11:30:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <81DE960F-C90C-4912-87EF-3E3C533EE3D2@gmail.com>
References: 
 <CAE1xAnspZx_HGgUUqT0PrQEftNTsm5L9JQNbNbo-2WDTq-LuMA@mail.gmail.com>
 <CAN_YF5yjaAUb-LkghiVeVTHiN5Mf2Jiy4HhOTMM+iC4LF81P9g@mail.gmail.com>
 <CAE1xAnvC0oGzvuOqkuOd+jF-Yt0pPU1WmKSKKMTJY7UxD+M7YQ@mail.gmail.com>
To: dev@asterixdb.incubator.apache.org

If fix for 2) will break the backwards-compatibility 1) might do that as =
well and be submitted together.

Now 2) was a long overdue problem, I don=E2=80=99t think there is any =
reason even to try make changes backwards-compatible, because it was =
broken in the first place.

> On Dec 14, 2015, at 11:16, Steven Jacobs <sjaco002@ucr.edu> wrote:
>=20
> It's a new attribute, but it's a closed field, which means it isn't
> backwards compatible.
> Steven
>=20
> On Mon, Dec 14, 2015 at 11:13 AM, Ian Maxon <imaxon@uci.edu> wrote:
>=20
>> For 1), I guess the question is whether it would be a backwards
>> compatible change. Since it's just a new attribute (right?...), and =
it
>> is also sort of a new feature rather than a fix for something that =
was
>> critically broken, I would tend toward putting it on master. If it's
>> not backwards compatible though maybe it needs more careful
>> consideration.
>>=20
>> -Ian
>>=20
>> On Mon, Dec 14, 2015 at 10:12 AM, Steven Jacobs <sjaco002@ucr.edu> =
wrote:
>>> Hi all,
>>> I'm implementing a change so that datasets can use datatypes from
>> alternate
>>> data verses (previously the type and set had to be from the same
>>> dataverse). Unfortunately this means another change for Dataset =
Metadata
>>> (which will now store the dataverse for its type).
>>>=20
>>> As such, I had a couple of questions:
>>>=20
>>> 1) Should this change be thrown into the release branch, as it is =
another
>>> Metadata change?
>>>=20
>>> 2) In implementing this change, I've been looking at the Metadata
>> secondary
>>> indexes. I had a discussion with Ildar, and it seems the thread on
>> Metadata
>>> secondary indexes being "hacked" has been lost. Is this also =
something
>> that
>>> should get into the release? Is there anyone currently looking at =
it?
>>>=20
>>> Steven
>>=20

Best regards,
Ildar