add PARTITION BY option for CopyInto

[azban]

Please answer these questions before submitting your pull requests. Thanks!

1. What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-878116: CopyInto does not support the PARTITION BY clause #430

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
   • I am adding new logging messages
   • I am adding new credentials
   • I am adding a new dependency

3. Please describe how your code solves the related issue.

This adds an argument to CopyInto which can be used to specify a string value for PARTITION BY. I have a few questions about implementation:

1. Would it be better to adhere to the convention of having functions that do some validation similar to those used for CopyInto.copy_options? If so, is there any particular validation to make sense?
2. Is there a preference towards implementing this as a clause rather than allowing for a string? I'm not very familiar with custom clauses, and I don't know of a similar implementation that would be useful to base this on.
3. Unrelated to implementation, but is there a straightforward way to run tests locally? i.e. is there an example parameters file that can be used?

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[azban]

I have read the CLA Document and I hereby sign the CLA

[azban]

recheck

[azban]

can anyone please take a look at this?

[azban]

what's the process for this repo considering and accepting PR's? should we assume we should maintain our own forks long-term?

[azban]

annual bump =/

[afavaro]

@sfc-gh-dszmolka @sfc-gh-astus @sfc-gh-mraba

Any chance we could get a review on this? We're still maintaining our own fork of this library so that we can use this feature.

[sfc-gh-dszmolka]

hi @afavaro and everyone; first of all, i regret it takes such a long time for the team to review this PR. I don't have any explanation which can be shared publicly.

However what I think could work, if you please reach out to your Snowflake account teams and express how this PR is important to you. This could help getting more attention on this PR, and hopefully, this product in general. Thank you in advance and I'm really sorry for this.

[sfc-gh-lcalderonachio]

Hi @azban
Thanks for your contribution, these changes have been merged in #542 with some additional changes. I'll be closing this PR now