Re: [Discuss] Iceberg View Interoperability

2024-12-05 Thread Weston Pace
Disclaimer: Also on Substrait SMC here and also have made some considerable investment into Substrait in my professional work (Lance) so this is an not unbiased opinion. I just want to give a few words on why I think an IR (and specifically Substrait) is not just another dialect (I'll try and be m

Re: [DISCUSS] Variant Spec Location

2024-08-16 Thread Weston Pace
in maintaining it in the Arrow community. The main > place where it is evolving right now (besides adding type IDs) is in > shredding and storage. > > > On Fri, Aug 16, 2024 at 9:59 AM Weston Pace wrote: > >> +1 to using Arrow to house the spec. In the interest of expediency I

Re: [DISCUSS] Variant Spec Location

2024-08-16 Thread Weston Pace
+1 to using Arrow to house the spec. In the interest of expediency I wonder if we could even store it there "on the side" while we figure out how to integrate the variant data type with Arrow. I have a question for those more familiar with the variant spec. Do we think it could be introduced as

Re: Iceberg Logo Fix and Iceberg Swag Shop

2023-12-06 Thread Weston Pace
me know if there are any > issues viewing them. > > On Wed, Dec 6, 2023 at 9:53 AM Weston Pace wrote: > >> BTW: ASF mailing lists strip attachments and so you will need to use a >> gist or some other sharing. >> >> On Wed, Dec 6, 2023, 7:22 AM Russell Spitzer &

Re: Iceberg Logo Fix and Iceberg Swag Shop

2023-12-06 Thread Weston Pace
BTW: ASF mailing lists strip attachments and so you will need to use a gist or some other sharing. On Wed, Dec 6, 2023, 7:22 AM Russell Spitzer wrote: > The original email has a broken png link so I was never able to see the > issue, could you attach the before and after so I can see the differe

Re: 【Feature】Request support for c++ sdk

2022-06-08 Thread Weston Pace
As Micah said, this would be pretty cool to use in Arrow datasets. I can't make any promises about helping develop it but if it were developed I could help integrate into Arrow datasets / Acero and provide some proof of concept. On Wed, Jun 8, 2022, 6:35 AM Ryan Blue wrote: > While I understand

Re: Slack invite

2021-07-08 Thread Weston Pace
n Thu, Jul 8, 2021, 3:15 PM Weston Pace wrote: > I added a comment to https://issues.apache.org/jira/browse/INFRA-21214 > and then I realized that someone has also opened > https://issues.apache.org/jira/browse/INFRA-22088 yesterday. I'm > happy to watch the link and add a r

Re: Slack invite

2021-07-08 Thread Weston Pace
URL occasionally stops functioning as it should. If the >> potential participant uses it and the submission form asks for an Apache >> email address, let Infra know so we can update the URL." >> >> Perhaps it is time to update the URL. >> >> thanks, >&

Re: Slack invite

2021-07-07 Thread Weston Pace
I believe you can join with a guest account using this link: https://s.apache.org/slack-invite More details: https://infra.apache.org/slack.html On Wed, Jul 7, 2021 at 9:15 AM Michiel De Smet wrote: > > HI, > > I would like a slack invite, it seems only apache.org addresses are allowed. > > Than

Re: Usage of parquet field_id

2021-05-20 Thread Weston Pace
hen we write back out > to a table, we use SQL semantics, which are to align by position. > > I hope that helps. If it's not clear, I'm happy to jump on a call to talk > through it with you. > > Ryan > > On Tue, May 18, 2021 at 1:48 PM Weston Pace wrote: >

Re: Usage of parquet field_id

2021-05-18 Thread Weston Pace
gt; they align with the Iceberg schema (in SQL this is done positionally). > > Let me know if any of that doesn't make sense. I'm still a little unclear on > the issue in #1, so it would be helpful if you could clarify that for me. > > Thanks, > Dan > > On Mon, M

Usage of parquet field_id

2021-05-17 Thread Weston Pace
ems the field_id/metadata should be erased in the third field but presumably it could also be the joined metadata from the two origin fields) Thanks for your time, -Weston Pace [1] https://issues.apache.org/jira/browse/PARQUET-1798 [2] https://github.com/apache/arrow/pull/10289 [3] https://issues.apa