bsovran commented on issue #41171: URL: https://github.com/apache/superset/issues/41171#issuecomment-4810872423
Happy to follow up in the Extensions Working Group meeting. https://github.com/apache/superset/pull/39171 doesn't fully solve the use case here, since atm its just a key value store, nothing tied to the underlying asset entities. Potentially extensions could have another mode where you pass in the asset type and id and it stores it within the extra field. That keeps a unified extensions storage api, but the actual entities are correctly tied strongly to the asset. To get better efficiency we can add an extra column to charts, dashboards, datasets, to hold jsonb value of extensions. This way when you ask for an array of assets we can get back the array of (asset, extension) pairs with little overhead. We keep the exact same CRUD on the assets themselves. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
