Treasure Data's primary idea portal. 

Submit your ideas & feature requests directly to our product requirements team! We look forward to hearing from you.

Add Job Meta Data

In anticipation of future features, can we begin logging / adding additional job parameters?


Job Type:

  • Via Console (Ad Hoc)
  • via API
  • Saved Query
    • Scheduled Run
    • user Triggered
  • Workflow Triggered
  • Data Connector
    • Scheduled Run
    • User Triggered


Based on the above, the related details

  • Workflow: ID / Name
  • Data Connector: Associated connection, transfer (Connector Name, e.g. sfdc_import_1484951229) , Target Object
  • Saved Query: Saved Query Name (e.g. queryId=88782)


This will be HUGE! I know this is forward looking, but we need to plant the seeds early...



  • Guest
  • Jan 30 2017
  • Likely to Implement
Active Requests?
Product Component Jobs
  • Admin
    Rob Parrish commented
    February 5, 2017 20:26

    As we've increased the systems that can submit jobs to Treasure Data - most recently with Treasure Workflow & Presto Direct API for BI Connectivity, it is important for us to give context as to where a job was submitted from. Particularly to help with error handling. We do plan to find a solution for this.