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.

Sign up for GitHub

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

Jump to bottom

potential bug for count(distinct JSON) #10215

Closed
XuHuaiyu opened this issue Apr 22, 2019 · 6 comments
Closed

potential bug for count(distinct JSON) #10215

XuHuaiyu opened this issue Apr 22, 2019 · 6 comments
Labels
challenge-program component/expression help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. invalid severity/moderate sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@XuHuaiyu
Copy link
Contributor

XuHuaiyu commented Apr 22, 2019 •
edited by ti-srebot
Loading

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

Theoretically, count(distinct JSON_cols) may have the same problem with #10099 as #10107 (comment) mentioned.

I did not build a case to trigger this successfully. Need more investigations.

SIG slack channel

#sig-exec

Score

  • 300

Mentor
@XuHuaiyu XuHuaiyu added type/bug The issue is confirmed as a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Apr 22, 2019
@XuHuaiyu XuHuaiyu mentioned this issue Apr 22, 2019
Closed
@zz-jason
Copy link
Member

the deadline of fixing this issue is?

@XuHuaiyu
Copy link
Contributor Author

Deadline is 2019-05-30.

@wjhuang2016
Copy link
Member

@XuHuaiyu PTAL

@ghost
Copy link

ghost commented Jul 16, 2020

I read the comment about not being comparable. Is it the same bug as #12233 ?

@ichn-hu ichn-hu mentioned this issue Nov 3, 2020
Closed
@XuHuaiyu
Copy link
Contributor Author

Can not reproduce, I'll close this issue

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
challenge-program component/expression help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. invalid severity/moderate sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@zz-jason @qw4990 @XuHuaiyu @wjhuang2016 @tisonkun @ti-srebot