Attendees

• Karim
• Aaron

Questions

• Adding a table
• From the convert
• Create table if not exists
• Need User/Role with create permissions
• Use table name in convert type UI
• One table per convert type/schema
• Variant table
• Will have standardize create command, other than table name
• Will need changes in Converttype UI to select columns, both top level and nested
• Noting profile and address standardization
• Non variant
• Could we add a checkbox view where users can decide what columns to choose?
• Will this break things?
• Auto-create the table
• Infer column types from convert
• SQL-compatible naming of columns
• Changes in the view
• Variant
• Like the table, per convert type
• message:data:{col name}::type as {col name} to top level unnested columns
• Nested columns will need standardized way to choose and build from converttype out
• Create/Update view checkbox in UI
• Create of in the data source
• Base datasource would use the output connection details
• Field definition creation would need to be figured out
• If there is no data in the table or view yet, we cannot interrogate data for field types