valid>
> > wrote:
> >
> >> Can a logical extension be based on another logical extension?
> >>
> >> HOCON support might be nice..
> >>
> >> -Original Message-
> >> From: Micah Kornfield
> >> Sent: Monday, November 28, 2022 11:50 AM
&g
extension be based on another logical extension?
HOCON support might be nice..
-Original Message-
From: Micah Kornfield
Sent: Monday, November 28, 2022 11:50 AM
To: dev@arrow.apache.org
Subject: Re: [DISCUSS] JSON Canonical Extension Type
External Email: Use caution with links
> Sent: Monday, November 28, 2022 11:50 AM
> To: dev@arrow.apache.org
> Subject: Re: [DISCUSS] JSON Canonical Extension Type
>
> External Email: Use caution with links and attachments
>
>
> This seems like a reasonable definition to me. Since there hasn't been
Can a logical extension be based on another logical extension?
HOCON support might be nice..
-Original Message-
From: Micah Kornfield
Sent: Monday, November 28, 2022 11:50 AM
To: dev@arrow.apache.org
Subject: Re: [DISCUSS] JSON Canonical Extension Type
External Email: Use caution
This seems like a reasonable definition to me. Since there hasn't been
much feedback, I think maybe following through an implementation + this
description in a PR would be the next steps. If there isn't further
feedback on this, once the PR is up we can have try to vote (which might
bring up
Hi folks!
I put together this specification for canonicalizing the JSON type in Arrow.
## Introduction
JSON is a widely used text based data interchange format. There are many
use cases where a user has a column whose contents are a JSON encoded
string. BigQuery's [JSON Type][1] and Parquet’s
