Hi,
It seems that null values can trigger a column to be treated as a numeric
one, in expressions evaluation, regardless of content or other indicators
and that fields in substructures can affect same-named-fields in parent
structure.
(1.2-SNAPSHOT, parquet files)
I have JSON data that can be red
Hi Stefan
This is the same old issue: Drill does an initial scan to determine the
type of a field. In cases where Drill encounters nulls in the data it
defaults to using a Nullable Int as the type (not a good choice perhaps).
This leads to all sorts of issues (most of which you're hitting).
T
This issue is addressed in DRILL-3477.
My proposed solution is to use VarBinary as the default type, as this has
the lowest precedence in the rules for implicit cast.
Making this change breaks some other things though, so I haven't been able
to merge the fix yet.
On Tue, Jul 28, 2015 at 2:23 PM,
Hi,
Would it not be possible to determine this on first-value or know if a
"unused default type" is being used and then change it once a value
presents it self?
Regards,
-Stefán
On Wed, Jul 29, 2015 at 1:59 AM, Steven Phillips
wrote:
> This issue is addressed in DRILL-3477.
>
> My proposed so
