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] - Not possbile to run query with _BULK and multiple lines #39

Closed
ChecksumDK opened this issue Nov 26, 2020 · 5 comments
Closed

[BUG] - Not possbile to run query with _BULK and multiple lines #39

ChecksumDK opened this issue Nov 26, 2020 · 5 comments
Assignees
Labels

Comments

@ChecksumDK
Copy link

I am trying to run the following valid lines, but the ´"Run Query" button is not available. The query runs fine with other tools.

POST /cmdb_nodes/_bulk

{ "index" : { "_index" : "cmdb_nodes", "_id" : "xxxx.xxx" } }
{"name": "xxx","system": "zzz","address": "11,4","nodeType": 1,"vendor": "yyy","model": "","manufactored": "1900-01-01T00:00:00","nodePath": "xxxx.xxx","description": "","reference": "","funcLoc": "na","cmdbType": 4,"properties": [],"linkInfo": "","status": 0},

Environment:

  • Elasticsearch version: 7.1
  • Operating system: Windows server 2019
  • Browser + version: Chrome 87.0.4280.66 (Official Build) (64-bit)
  • Elasticvue version: 0.30.0
  • Running elasticvue as a chrome browser extension:

Screenshots
Screenshot_1

@ChecksumDK
Copy link
Author

Can I test the updated version somehow?

@cars10
Copy link
Owner

cars10 commented Nov 30, 2020

Yes! I did not release a new version yet, but you can always build elasticvue on your own. Checkout the wiki for instructions.

@ChecksumDK
Copy link
Author

Don't know if it is a bug, but commented out lines like
//lorem ipsum
causes the query button to be disabled as well.

@cars10
Copy link
Owner

cars10 commented Nov 30, 2020

Right now the form checks if your request body is valid json. If it is invalid the button is disabled to prevent you from sending invalid data. Comments are not valid json, so the button is disabled. Maybe i should remove that feature and instead show a warning if invalid json is found :)

@cars10
Copy link
Owner

cars10 commented Dec 1, 2020

Implemented in version 0.31.0. Thanks again for your feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants