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

Sql lab search but don't have header. How can I solve it? #20038

Closed
lqiuhong opened this issue May 12, 2022 · 2 comments
Closed

Sql lab search but don't have header. How can I solve it? #20038

lqiuhong opened this issue May 12, 2022 · 2 comments
Labels
#bug Bug report

Comments

@lqiuhong
Copy link

image

@lqiuhong lqiuhong added the #bug Bug report label May 12, 2022
@yousoph
Copy link
Member

yousoph commented May 12, 2022

Hi @lqiuhong ,

Search in the SQL Lab text editor was enabled with this change: #19328
Is that what you're looking for?
If not, can you please clarify the issue and fill out the bug report template (below)?

Thanks!


A clear and concise description of what the bug is.

How to reproduce the bug

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected results

what you expected to happen.

Actual results

what actually happens.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

(please complete the following information):

  • browser type and version:
  • superset version: superset version
  • python version: python --version
  • node.js version: node -v
  • any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@rusackas
Copy link
Member

rusackas commented Feb 6, 2024

This is likely fixed by now, and is pretty out of date if not. If people are still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem.

@rusackas rusackas closed this as completed Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

3 participants