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

add thrift version 0.9.3 to requirements #3303

Closed
wants to merge 1 commit into from
Closed

add thrift version 0.9.3 to requirements #3303

wants to merge 1 commit into from

Conversation

alon710
Copy link
Contributor

@alon710 alon710 commented Jan 17, 2019

No description provided.

@request-info
Copy link

request-info bot commented Jan 17, 2019

We would appreciate it if you could provide us with more info about this issue/pr!

@request-info request-info bot added the Needs More Information Seen by a team member, not ready for a full review label Jan 17, 2019
@ghost ghost added the in progress label Jan 17, 2019
@alon710
Copy link
Contributor Author

alon710 commented Jan 17, 2019

Continue of PR #2410

@arikfr arikfr added PR: unreviewed and removed in progress Needs More Information Seen by a team member, not ready for a full review labels Jan 23, 2019
@arikfr
Copy link
Member

arikfr commented Oct 24, 2019

The reason it wasn't merged until now is that we don't have a way to know the impact of pinning the Thrift version on all the data sources that use it.

Until we have better test coverage (#3807) for our query runners or someone from the community can test it with the different ones that use Thrift, we won't be able to merge it :-(

@arikfr
Copy link
Member

arikfr commented Jan 21, 2020

Hi,

(This is a template message, but I mean every word of it. Also you're welcome to reply)

Thank you for making this contribution. While we couldn't bring it to completion and merge, it's still very much appreciated. 🙇

In the past year the Redash code base gone under massive updates: on the backend we moved to Python 3 & RQ instead of Celery and on the frontend we replaced Angular with React. It's very likely this makes this PR irrelevant without significant changes. :-(

I'm closing this PR now. But if you're still interested in making it happen, let me know and I will reopen.

Thanks.

@arikfr arikfr closed this Jan 21, 2020
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.

2 participants