... sound of crickets on a summer night .
It would really help me if I could get a response to this inquiry, to help
me better understand Drill.
I do realize people are busy, and also this was originally sent Aug 25,
which is the wrong time of year to get timely response to anything.
Hence, t
I'm thinking whether a first prototype of DFDL integration to Drill should
just use JSON.
But please consider this JSON:
{ "record": [
{ "a": { "a1":5, "a2":6 } },
{ "b": { "b1":55, "b2":66, "b3":77 } }
{ "a": { "a1":7, "a2":8 } },
{ "b": { "b1":77, "b2":88, "b3":99 } }
] }
It
Hi Mike,
I believe I sent a detailed response to this. Did it get through? If not,
I'll try sending it again...
- Paul
On Wed, Sep 13, 2023 at 6:44 AM Mike Beckerle wrote:
> ... sound of crickets on a summer night .
>
> It would really help me if I could get a response to this inquiry, to
Hi Mike,
Looks like you are wrestling with two separate issues. The first is how to
read the encoded data that you showed. In Drill, each data format generally
needs its own reader. Drill's reader operator provides all the plumbing
needed to handle multiple format readers, pack data into vectors,
