We're Moving!

The Vertica Forum is moving to a new OpenText Analytics Database (Vertica) Community.

Join us there to post discussion topics, learn about

product releases, share tips, access the blog, and much more.

Create My New Community Account Now


Tell us your data loading preferences — Vertica Forum

Tell us your data loading preferences

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!

https://in.hotjar.com/s?siteId=438341&surveyId=91386

Comments

  • ScottLScottL Employee

    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

  • ScottLScottL Employee

    I'll move this to it's own post! :)

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file