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

update datafusion to 42 #44

Closed
wants to merge 1 commit into from
Closed

update datafusion to 42 #44

wants to merge 1 commit into from

Conversation

davidhewitt
Copy link
Collaborator

Waiting on datafusion 42 release (any day now).

Comment on lines +947 to +952
// #[tokio::test]
// async fn test_lexical_precedence_wrong() {
// let sql = r#"select '{"a": "b"}'->>'a'='b' as v"#;
// let err = run_query(sql).await.unwrap_err();
// assert_eq!(err.to_string(), "Error during planning: Unexpected argument type to 'json_as_text' at position 2, expected string or int, got Boolean.")
// }
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@samuelcolvin I assume this test was documenting broken parse precedence and we can now just remove it?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Or update it to test the successful case?)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I'll fix.

@hengfeiyang
Copy link

Datafusion already release 42

@samuelcolvin
Copy link
Collaborator

superceded by #47, it was easier to create a new PR due to conflicts. We can close this once we're no longer using a sha from this branch in logfire.

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