RFC: Legend Query Production Workflows

[MauricioUyaguari]

Overview

Discussion around workflows in legend query in regards to productionizing queries

Dataspace Specification

public class DataSpace extends PackageableElement
{
    public List<StereotypePtr> stereotypes = Collections.emptyList();
    public List<TaggedValue> taggedValues = Collections.emptyList();

    public List<DataSpaceExecutionContext> executionContexts;
    public String defaultExecutionContext;

    public String title;
    public String description;
    public List<PackageableElementPointer> featuredDiagrams;
    public DataSpaceSupportInfo supportInfo;
}

Entry Points for Legend Query

• Dataspace
• LoadExistingQuery
• LoadServiceQuery
• CreateNewQuery

Workflow for dataspaces

• Team 1 (Tech Team)
  • studio create metadata for query
    • classes, stores, mapping, runtime (could we split into 2 teams, one creating models diagrams and the other mappings, runtimes)
  • studio create dataspace
  • merge changes + release (available in depot)
• Team 2
  • open relevant dataspace using gav coordinates

Questions/Concerns

• Should we allow CreateNewQuery or should we only allow creating

Promote To Service Action @akphi @MauricioUyaguari Agreed

• Query to Service 1-1
• Upon promoting query to service we will add queryId to service tagged values (add to metamodel) and add service coordinates to queryId.
• From then on query will continue to be editable, upon save users will have option to saver existing query or update service

Promote to Service States:

• DataspaceQueryBuilderState
  • what should our messaging be about how users should set up project. One project for producers, another for consumers?
  • If so, query should live in consumer ? or separate project
  • Possibly add dataspace configurations that can specified service output project
  • Do we allow promoting service without saving the query first
• ServiceQueryBuilderState
• CreateNewQueryBuilderState

Save to SDLC

• Create Project, Request Entitlement

Agreed

• decoupling from the query as soon as you promote to query
• Add Register Dev (semi interactive)
• Promote to Service (Only Devs will do this)
• Business users wont understand