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

bug: Unable to get field named "114" #16564

Open
1 of 2 tasks
rad-pat opened this issue Oct 3, 2024 · 2 comments
Open
1 of 2 tasks

bug: Unable to get field named "114" #16564

rad-pat opened this issue Oct 3, 2024 · 2 comments
Labels
C-bug Category: something isn't working

Comments

@rad-pat
Copy link

rad-pat commented Oct 3, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

Version

v1.2.642-nightly

What's Wrong?

APIError: ResponseError with 1006: Unable to get field named "114". Valid fields: []

I've no idea what this is referring to. There is no field "114" within my query

How to Reproduce?

Quite a long and complicated query using many CTE, this has been working fine on previous used version 1.2.635-nightly

CREATE OR REPLACE TABLE t1 (test bigint);

WITH cte1
AS (
	SELECT t1.test
	FROM t1
	WHERE t1.test = 0
	)
	,cte2
AS (
	SELECT cte1.test
	FROM cte1
	WHERE cte1.test = 1
	
	UNION ALL
	
	SELECT cte1.test
	FROM cte1
	WHERE cte1.test = 0
	)
SELECT *
FROM cte2;

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@rad-pat rad-pat added the C-bug Category: something isn't working label Oct 3, 2024
@wubx
Copy link
Member

wubx commented Oct 4, 2024

You can provide the taable structure and query SQL.

@rad-pat
Copy link
Author

rad-pat commented Oct 4, 2024

You can provide the taable structure and query SQL.

@wubx , I managed to reproduce with a much simpler query. Issue updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants