GitHub user sshiv012 added a comment to the discussion: Support external and domain-specific code integrations
I may be misunderstanding the intended context, but is this about supporting domain-specific or “flavored” Texera deployments? I am thinking of models such as PostgreSQL’s extension ecosystem, or AsterixDB-based projects such as Graphix and Big Active Data, where domain-specific functionality is maintained separately from the core system. AsterixDB also documents a mechanism for including external extension modules in custom binary assemblies as bill of materials (BOM) If this is the intended use case, a patching approach makes sense. Each flavor could live in a separate repository containing: - A pinned Texera version. - A versioned patch series. - Additional services or containers. - Domain-specific configuration. - CI verifying that the patches apply and the deployment builds. This would keep domain-specific maintenance outside the Texera repository while making each deployment reproducible. Is that close to the integration model being proposed? GitHub link: https://github.com/apache/texera/discussions/6727#discussioncomment-17744178 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
