Skip to content

GSIP 135b

Jody Garnett edited this page Jul 12, 2017 · 1 revision

GSIP 135 - Setting of default data store

Overview

The catalog forces a workspace default datastore to be the first loaded. Allow default datastore to remain unset unless a value is provided by the user (via GUI or REST API).

This change will allow Importer to default to "Create New", unless the user has defined a default data store for a workspace.

Proposed By

Morgan Thompson

Assigned to Release

State

  • Under Discussion
  • In Progress
  • Completed
  • Rejected
  • Deferred

Motivation

Currently the catalog forces the default store to be the first store (alphabetically) in the workspace.

Proposal

The CatalogImpl addStore method will capture the first datastore added for use as a default, we would like to remove this code (and the assumption that every datastore will have a default workspace).

This change will allow the Importer to detect when a default has been set for a workspace, and otherwise default to "Create New". A checkbox to set the default store will be added to the store creation and editting pages. Additionally a "default" column for the store view table (ie. as in the workspace view table), the table will have to be sorted by workspace name to make it readable.

Feedback

Backwards Compatibility

Voting

Project Steering Committee:

  • Alessio Fabiani:
  • Andrea Aime:
  • Ben Caradoc-Davies: +0
  • Christian Mueller:
  • Jody Garnett:
  • Jukka Rahkonen:
  • Phil Scadden:
  • Simone Giannecchini:

Committers:

Links

Clone this wiki locally