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

[Subtask] Support Expression system #5201

Open
Tracked by #5198
unknowntpo opened this issue Oct 21, 2024 · 3 comments · May be fixed by #5646
Open
Tracked by #5198

[Subtask] Support Expression system #5201

unknowntpo opened this issue Oct 21, 2024 · 3 comments · May be fixed by #5646
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@unknowntpo
Copy link
Contributor

Describe the subtask

Support Expression system
docs
related java issue: #600

Parent issue

#5198

@unknowntpo unknowntpo added the subtask Subtasks of umbrella issue label Oct 21, 2024
@SophieTech88
Copy link
Contributor

Can I work on this issue?

@SophieTech88
Copy link
Contributor

I noticed that the file expressions/Literal.java includes the comment: @deprecated This interface will be removed. Additionally, there’s a folder expressions/literals/ containing two files: Literal.java and Literals.java.

For the Python client, which of these files should I implement? Should I focus on the new implementation in expressions/literals/, or is there a need to maintain compatibility with the deprecated interface?

@SophieTech88
Copy link
Contributor

Another question: under the expressions folder, there are several subfolders like distributions, sorts, transforms, and literals, as well as files such as Expression.java, FunctionExpression.java, Literal.java, NamedReference.java, and UnparsedExpression.java.

Could you confirm if all of these need to be converted into Python client interfaces, or are there specific ones I should focus on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subtask Subtasks of umbrella issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants