Treasure Data

Welcome to our feedback forum. Let us know how we can improve your experience with our product.

I think Treasure Data should...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Support for an additional key like "Description" in job list hash

    It would be great if we chould have an additional key that refers to "for what is this job" in order to identfy jobs.

    As of now, it is difficult to pick up the right job by any keys. It would be problematic when monitoring.

    6 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  API  ·  Admin →
    • Expose "# of result rows" information to REST API (/v3/job/show/:job_id)

      Currently, API cannot return # of result rows for each Jobs. It would be great to have that information to validate the result without downloading the result itself.

      5 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  API  ·  Admin →
      • `td table:create` disables v-column by default.

        Currently, `td table:create` ables v-column by default.

        But when we create tables via console, it disables v-column by default.
        We want to arrange the state of that.

        3 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  API  ·  Admin →
        • Support adding column metadata through the REST API and/or CLI

          Currently, we don't support adding column metadata (e.g. column description) via td command line.
          Some folks would like to be able to do that as opposed to using the Console by going to Console>Databases>Table>Metadata.

          3 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            1 comment  ·  API  ·  Admin →
          • Move table from one DB to another DB

            There is no easy way to migrate table from one DB to another.
            Because, we need to run query if user want to migrate table between 2 DBs.
            For example,

            1. td table:create databaseB tableA
            2. Issue query: `insert into databaseB.tableA select * from databaseA.tableA`
            3. td table:delete databaseA tableA

            So, if the table was too huge, it would be needed too much resources.
            Expected Results

            Support the following feature.
            td table:move . .

            3 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  API  ·  Admin →
            • Support a feature to expire table after specified number of days

              We want to expire table after specified number of days, it's similar feature like td table:expire.

              Because, our databases are crowded with a lot of temporary table and unnecessary table when we free our end users to use TD.

              So, currently, we need to make a lot of rules to use TD.

              If this feature is supported, we could organize our tables in database easily.
              We just say to our end-user, "please set this option when you create temporary tables"

              2 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  API  ·  Admin →
              • Expose TD dashboard monitoring metrics via REST API

                Expose TD dashboard monitoring metrics via REST API. Would help in building alerts around metrics programmatically.

                2 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  1 comment  ·  API  ·  Admin →
                • Unification of DataConnector's guess/issue specifications via cli and client API.

                  We use td-toolbelt and client API (via python or ruby).
                  When we make DataConnector's yaml file via td-toolbelt and use it via client API, a error occurs.
                  This cause is by difference of a yaml file format.
                  The client API refuses yaml file which is made from td-toolbelt because the first line is not "config:".

                  -td-toolbelt guess result
                  ====
                  --- # <- this is the cause of error.
                  in:
                  type: s3
                  access_key_id: ***
                  secret_access_key: ***
                  ...
                  ====

                  -API guess result
                  ====
                  config:
                  exec: {}
                  filters: []
                  in:
                  access_key_id: ***
                  bucket: ***
                  ...
                  ====

                  We want to use same yaml file…

                  2 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  API  ·  Admin →
                  • URL about DBs and Tables.

                    Now, DBs and Tables are paid out unique numbers as below:

                    https://console.treasuredata.com/databases/43732
                    https://console.treasuredata.com/databases/43732/tables/1231816

                    But we often want to use URL with its name (not unique number) to write our documents and so on.
                    For example, we drop a DB/table and recover it with same name in some cases when the trouble occurs.Then, we must re-write our documents about its links.

                    expected URLs)
                    https://console.treasuredata.com/databases/database1
                    https://console.treasuredata.com/databases/database1/tables/table1

                    2 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  API  ·  Admin →
                    • User Management API

                      Please provide the user management API.
                      It's hard to manage a lot of users from the console.

                      1 vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  API  ·  Admin →
                      • Query's permission on Saved queries.

                        We have saved queries which is usually executed from our system.
                        But now, it's sometimes carried out from other routes.
                        We don't want to run it on other people/routes because unexpected export data affects our system processing.

                        So we want a permission feature about saved queries, not DB access control.

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          1 comment  ·  API  ·  Admin →
                        • Don't see your idea?

                        Treasure Data

                        Feedback and Knowledge Base