s3export
Hi,
Where can I find documentation about this function ? limitations, errors ?
I have a table with 1130 columns/ 13 millions rows and I am trying to export it to s3.
All columns are exported (about 400 files created) but not all rows.
I obtained the following error:
SQL Error [5861] [VP001]: [Vertica][VJDBC](5861) ERROR: Error calling processPartition() in User Function s3export at [src/S3.cpp:540], error code: 0, message: Numeric output buffer too small
[Vertica][VJDBC](5861) ERROR: Error calling processPartition() in User Function s3export at [src/S3.cpp:540], error code: 0, message: Numeric output buffer too small
com.vertica.util.ServerException: [Vertica][VJDBC](5861) ERROR: Error calling processPartition() in User Function s3export at [src/S3.cpp:540], error code: 0, message: Numeric output buffer too small
Thank you,
Veronica
Comments
Hello,
I am having the same problem.
Were you ever able to resolve this?
Thanks,
Drew
Here:
https://my.vertica.com/docs/8.1.x/HTML/index.htm#Authoring/AdministratorsGuide/BulkLoadCOPY/AWSLibrary/exportAWSlibrary.htm?Highlight=s3export
Hi @ckotsidimos -- I've read the manual many times. I'm not sure what I'm missing.
Here is the exact error message I get:
17:09:47 [SELECT - 0 rows, 1778.340 secs] [Code: 5861, SQL State: VP001] [Vertica]VJDBC ERROR: Error calling processPartition() in User Function s3export at [src/AWSHttpClient.cpp:259], error code: 0, message: MethodNotAllowed (405): The specified method is not allowed against this resource.
... 4 statement(s) executed, 0 rows affected, exec/fetch time: 1778.856/0.000 sec [3 successful, 1 errors]
Hi @ScubaDrew
What version of vertica are you using?
You may encounter that error sometimes when s3export aborts. It tries to clean up by deleting partial uploads, but there is nothing to clean up.
@asaeidi 07.02.0300
@asaeidi Is there any way to determine why it aborted?
From my vertica logs:
no, I wasn't able to use s3export for large tables.
@ScubaDrew sorry for the delay. 7.2.3 is the first version we introduced the S3 connector. Could you upgrade to a newer version, and see if the problem still exists?
Our time with Vertica has come to an end. We will not be doing any further upgrades. My two years dealing Vertica has been filled with issues like this. Incomplete and non-function software for even basic tasks. Thanks for the suggestion @asaeidi -- but off to RedShift we go!