Skip to content

Conversation

@lyndsiWilliams
Copy link
Member

SUMMARY

Move the existing fields from the "Extra" section to the following sections. This also includes splitting the JSON field in "Other" and the metadata_cache_timeout field into multiple fields. The extra fields now live in the following locations:

  • SQL Lab

    • Enable query cost estimation (allows_virtual_table_explore)
    • Allow this database to be explored (cost_query_enabled)
  • Performance

    • Metadata Cache Timeout with Schema and Table options

      metadata_cache_timeout: {
          schema_cache_timeout,
          table_cache_timeout,
      }
      
  • Security

    • Schema select for uploading data (schemas_allowed_for_csv_upload)
    • Impersonate logged in user (impersonate_user)
    • Allow data upload (allow_csv_upload)
  • Other

    • engine_params and metadata params (in separate json fields)
    • version

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

  • ---------- BEFORE ----------

    SQL Lab
    sqllab-before

    Performance
    performance-before

    Security
    security-before

    Other
    other-before

  • ---------- AFTER ----------

    SQL Lab
    sqllab-after

    Performance
    performance-after

    Security

    security-after-1 security-after-2

    Other
    other-after

TEST PLAN

  1. From the "Databases" page, open the database modal by clicking either the "+ DATABASE" button or the "Edit" action button on any listed database.
  2. Observe the described changes on the following tabs: SQL Lab, Performance, Security, Other

ADDITIONAL INFORMATION

  • Has associated issue: Clubhouse Ticket
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@lyndsiWilliams lyndsiWilliams changed the title Move extra fields refactor: Move fields from Extra section IIII Jun 9, 2021
key="1"
>
<StyledInputContainer className="mb-0">
<StyledInputContainer css={{ ...no_margin_bottom }}>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does css={no_margin_bottom} work here? Should be the same thing.

// };

// Add values back to extra field
update.extra = JSON.stringify(db?.extra_json, null, ' ');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about the idea to store this in the db object as a string and then parse it out in the extraOptions component? So you don't have to manipulate anything here.

@lyndsiWilliams lyndsiWilliams force-pushed the lyndsi/move-extra-fields-4 branch from 296917c to 2cbe5a6 Compare June 10, 2021 20:29
@lyndsiWilliams lyndsiWilliams deleted the lyndsi/move-extra-fields-4 branch July 12, 2021 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants