asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abdullah alamoudi <>
Subject Re: Question about open indexes
Date Tue, 22 Sep 2015 06:25:41 GMT
More thoughts:
I assume the intention of the cast was just to make sure if the open field
exists, it is of the specified type. Moreover, the un-casted record should
be inserted into the index.
If my assumptions are not correct, please, let me know ASAP.

I have two thoughts on this:
1. Actually, insert plans show that the records being inserted into the
primary index is actually the casted record creating the issue described

2. I don't believe this is the right way to ensure that the open field if
exists is of the right type. why not extract the field using field access
by name function and then verify the type using the field tag?

On Tue, Sep 22, 2015 at 9:11 AM, abdullah alamoudi <>

> Hi Dev, @Ildar,
> In the insert pipeline for datasets with open indexes, we introduce a cast
> function before the insert and so one would expect the records to look like
> the casted record type which I assume has {{the closed fields + a nullable
> field}}.
> The question is, what happens to the previously existing records?, since
> now the index has both, records of the original type and records of the
> casted type.
> Thanks,
> Abdullah.

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