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

split_part returns result from previous row when current row does not have the part #4489

Closed
1 task done
DSroD opened this issue May 9, 2024 · 1 comment · Fixed by #4493
Closed
1 task done
Assignees
Labels
Bug Incorrect or unexpected behavior SQL Issues or changes relating to SQL execution

Comments

@DSroD
Copy link

DSroD commented May 9, 2024

To reproduce

Executing following query

select split_part(x, '.', 3) from
(select 'a.b' as x
union select 'c.d' as x
union select 'e.f.g' as x
union select 'h.i.j' as x
union select 'k.l' as x
union select 'm.n' as x)

returns

split_part
g
j
j
j

Expected result would be

split_part
g
j

When executed in Web Console multiple times in a row, first two rows are also populated with data from previous execution.

QuestDB version:

7.4.2

OS, in case of Docker specify Docker and the Host OS:

Ubuntu 22.04 (Docker)

File System, in case of Docker specify Host File System:

ext4

Full Name:

Daniel Rod

Affiliation:

Second Foundation

Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?

  • Yes, I have

Additional context

Screenshot 2024-05-09 at 18 34 05
@nwoolmer nwoolmer self-assigned this May 10, 2024
@nwoolmer nwoolmer added Bug Incorrect or unexpected behavior SQL Issues or changes relating to SQL execution labels May 10, 2024
@nwoolmer
Copy link
Contributor

Hi @DSroD , thanks for the report and repro, bugfix will be in next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Incorrect or unexpected behavior SQL Issues or changes relating to SQL execution
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants