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

[PECO-1926] Create a non pyarrow flow to handle small results for the column set #440

Merged
merged 6 commits into from
Oct 3, 2024

Conversation

jprakash-db
Copy link
Contributor

@jprakash-db jprakash-db commented Sep 13, 2024

PECO-1926

Description

To handle the flow of result when pyarrow is not present. This setup is particularly used for users who want to handle small quantities of data

Task Completed

  • Introduced the new non arrow flow for data to be handled by the users not having pyarrow
  • ColumnQueue is the new ResultSetQueue that I have added to handle the column set data
  • Entire pipeline of handling the column set data to finally converting it to the TRow type for the user has been implemented
  • Added tests for the ColumnQueue to ensure that it is working as intended

Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

@jprakash-db jprakash-db marked this pull request as draft September 13, 2024 08:40
@jprakash-db jprakash-db marked this pull request as ready for review September 13, 2024 08:52
@kravets-levko kravets-levko changed the title [ PECO-1926 ] Create a non pyarrow flow to handle small results for the column set [PECO-1926] Create a non pyarrow flow to handle small results for the column set Sep 16, 2024
Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

src/databricks/sql/thrift_backend.py Outdated Show resolved Hide resolved
src/databricks/sqlalchemy/pytest.ini Outdated Show resolved Hide resolved
Copy link

github-actions bot commented Oct 3, 2024

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

@kravets-levko kravets-levko merged commit a151df2 into main Oct 3, 2024
9 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants