trino
trino copied to clipboard
fix compiler failure with regexp_replace function when working with Hive tables containing row(map<varchar, varchar>) data type
Additional context and related issues
fix #19689
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla
Cla pdf on appendix
------------------ Original ------------------ From: cla-bot[bot] @.> Date: Wed,Nov 15,2023 4:06 PM To: trinodb/trino @.> Cc: needlssj @.>, Author @.> Subject: Re: [trinodb/trino] fix compiler failure with regexp_replace functionwhen working with Hive tables containing row(map<varchar, varchar>) data type(PR #19749)
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to @.*** Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
:wave: @needlssj - this PR has become inactive. If you're still interested in working on it, please let us know, and we can try to get reviewers to help with that.
We're working on closing out old and inactive PRs, so if you're too busy or this has too many merge conflicts to be worth picking back up, we'll be making another pass to close it out in a few weeks.
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
@findepi @findinpath @alexjo2144 @electrum is there merit in this PR and fix or should we close?
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
Apologies for the delay in reviewing this. Can you share a reproduction?
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time.
Reopened and added stale-ignore .. fyi @findepi and @electrum
This might have been solved by https://github.com/trinodb/trino/pull/20226.
@takezoe indeed, thanks.