Ideas

Treasure Data's primary idea portal. 

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

Support Query Versioning for Saved Queries

Many saved queries would get iterated over time, yet sometimes people do need to go back to an earlier version to test out something, while don't want to change the existing latest version.

  • Mengke Li
  • Aug 19 2016
  • Under Review
Active Requests?
Product Component Query Editor
  • Ryutaro Yada commented
    September 2, 2016 04:02

    This will be nice to be released with https://treasure-data.ideas.aha.io/ideas/CON-I-18.

    Saved queries are like batch programs managed and maintenanced by team.
    Query maintenance history(who, when, how modified) and execution history(when executed by which version) are useful and important for auditing and trouble shooting.

  • Kazuki Ohta commented
    January 30, 2017 22:34

    While we understand version management of saved queries are important, we now have a great alternative. Using workflow + Git repository. In this way, teams with multiple people can modify the data pipeline together with revision management. Please try this for now.

    • ¬†https://docs.treasuredata.com/articles/workflows-continous-deployment