-
Notifications
You must be signed in to change notification settings - Fork 333
Snowflake export update #3124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Snowflake export update #3124
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -202,10 +202,6 @@ public void writeRows(RowWriter rowWriter) | |
| throw (ex instanceof RuntimeException) ? (RuntimeException) ex : new RuntimeException(ex); | ||
| } | ||
|
|
||
| if (rows > maxRowsPerCall) { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why is this no longer needed? or better question; why did we need
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and it seems to be used only within this method; if not needed should we clean up the rest of the class and the constructor? but only after we answer the first question; i.e. why we no longer need max rows per call
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The initial was to prevent |
||
| throw new AthenaConnectorException("Call generated more than " + maxRowsPerCall + "rows. Generating " + | ||
| "too many rows per call to writeRows(...) can result in blocks that exceed the max size.", ErrorDetails.builder().errorCode(FederationSourceErrorCode.INVALID_INPUT_EXCEPTION.toString()).build()); | ||
| } | ||
| if (rows > 0) { | ||
| block.setRowCount(rowCount + rows); | ||
| } | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -52,6 +52,7 @@ public enum SupportedTypes | |
| VARCHAR(Types.MinorType.VARCHAR), | ||
| STRUCT(Types.MinorType.STRUCT), | ||
| LIST(Types.MinorType.LIST), | ||
| TIMESTAMPNTZ(Types.MinorType.TIMESTAMPMILLI), | ||
|
||
| MAP(Types.MinorType.MAP); | ||
|
|
||
| private Types.MinorType arrowMinorType; | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
discussing this offline; but just for the sake of keeping this PR in the loop; is
allocateNew()required now in the newer version? Since we never actually had to do this before? and is the default allocation good enough initially?