Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE]: Organize GitHub repos for Multiplexer project #1290

Open
1 task done
Tracked by #1297
ericvergnaud opened this issue Dec 5, 2024 · 2 comments
Open
1 task done
Tracked by #1297

[FEATURE]: Organize GitHub repos for Multiplexer project #1290

ericvergnaud opened this issue Dec 5, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@ericvergnaud
Copy link
Contributor

ericvergnaud commented Dec 5, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Category of feature request

Transpile

Problem statement

As part of implementing the Multiplexer, we will be producing a number of artifacts:

a) Skeletons:

  • skeleton for Python
  • skeleton for Typescript
  • skeleton for Scala
  • etc...

b) Transpilers

  • SnowFlake python (MVP) (OSS)
  • SnowFlake scala transpiler (closed source)
  • T-SQL scala transpiler (closed source)
  • DBT scala transpiler (closed source)

We need to store the corresponding code into appropriate repos.
We currently have only 1 repo: remorph.
The purpose of this issue is to agree on which repos to create

Proposed Solution

For example:

  • a public multiplexer-skeletons repo for all skeletons and docs
  • a public snowflake-transpiler for the python/sqlglot tsnowflake transpiler
  • a private snowflake-converter for the scala snowflake transpiler
    etc...

Additional Context

No response

@ericvergnaud ericvergnaud added the enhancement New feature or request label Dec 5, 2024
@jimidle
Copy link
Contributor

jimidle commented Dec 5, 2024

We will get into dependency hell potentially. Maven can build complete jars with dependencies, but is this the right time to start splitting this up?

We would probably need a Maven artifact repo as well, though I suspect there is already one somewhere. Getting the Python into its own project seems like a good idea though. Needs some discussion I think.

@ericvergnaud
Copy link
Contributor Author

ericvergnaud commented Dec 9, 2024

@asnare @vil1 @sundarshankar89 your comments would be welcome 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants