Tell us your data loading preferences
![[Deleted User]](https://us.v-cdn.net/6029397/uploads/defaultavatar/nD0LWW9MQTB29.jpg)
[Deleted User]
Administrator
We’re back with our newest product management survey for this summer! This time we’re asking about how you load your data – everything from the ETL tools you use to how you manage your information. The answers you provide will help us fit Vertica into your infrastructure in a way that is ideal for your needs. Click below to take the survey and thank you for your investment in improving Vertica!
1
Comments
Speaking of data loading!
We have a question about the ApportionedLoad process.
We were unclear as to whether 1 UDF could cover all the different loads or would there be 1 UDF for each load? From reading the 9.1 doco, it looks like the UDParser step would require a specific parser for each table so multiple UDFs would have to be written.
You use three types of UDL functions during development, one for each stage of the data-load process:
[omitted the first two]
• User-Defined Parser (UDParser): Up to one parser parses the data into tuples that are ready to be inserted into a table. For example, a parser could extract data from an XML-like format. You can optionally define a User-Defined Chunker (UDChunker, C++ only), to have the parser perform parallel parsing.
Can someone confirm?
Thanks
I'll move this to it's own post!