BenikamSrikar commented on issue #41171: URL: https://github.com/apache/superset/issues/41171#issuecomment-4738528205
Hi @bsovran, this looks like a clean, well-scoped proposal — thanks for writing it up. I'd like to take a shot at implementing this if it's cleared to proceed. A bit of context: I'm a CS student with hands-on experience building backend systems (Node.js/Express, REST APIs) and solid coursework in DBMS, so I'm comfortable with the data modeling and migration side of this (nullable column, MediumText, Alembic upgrade/downgrade). I haven't contributed to Superset before, so I'll be ramping up on the codebase conventions as I go, but I'm happy to put in the time to get it right and iterate on review feedback. Before I start: is this SIP considered approved to implement, or does it still need broader discussion/a vote given it touches the data model? Want to make sure I'm not jumping ahead of the process. If it's good to go, I'll start with the Slice model field + migration + import/export field addition as scoped, and open a draft PR early so you can sanity-check direction before I go further. -- 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]
