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

A search with an empty fields param causes a NullPointerException or a runaway process #55

Closed
clintongormley opened this issue Mar 10, 2010 · 2 comments
Closed

A search with an empty fields param causes a NullPointerException or a runaway process #55

clintongormley opened this issue Mar 10, 2010 · 2 comments
Labels
>bug v0.06.0

Comments

@clintongormley
Copy link

Hiya

An empty fields[] array either returns a NullPointerException, or causes a runaway process. Try this:

curl -XGET 'http://192.168.5.100:9200/_all/_search'  -d '
{
   "fields" : [],
   "query" : {
      "matchAll" : {}
   }
}
'

thanks

Clint
@kimchy
Copy link
Member

kimchy commented Mar 10, 2010

A search with an empty fields param causes a NullPointerException or a runaway process. Changed logic for an empty fields array, where it won't return the source in this case. Closed by 4b04db9.

@clintongormley
Copy link
Author

fixed++

beiske added a commit that referenced this issue Jun 5, 2015
@beiske @dadoonet
Add per repository credentials
7f271fd 
Changed AwsS3Service to use one client per region and credentials combination.
Made S3Repository specify credentials if such exists in the repository settings.

Updated readme with repository specific credentials settings.

Closes #54.
Closes #55.
Closes #56.
(cherry picked from commit d4ea2dd)
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
StefanGor pushed a commit to StefanGor/elasticsearch that referenced this issue Mar 17, 2017
@kblincoe
Merge pull request elastic#55 from gwyneth-bassett/patch-1
4821a8a 
Update Coordination.md
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue May 24, 2018
@DaveCTurner
Integrate Legislator with ClusterApplier (elastic#55)
20bfb74 
A true Discovery implementation must expose newly-committed cluster states to
the rest of the system via the ClusterApplier interface. This change adds this
functionality to the Legislator.
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
@matt-davis-elastic
Fixing some grammar issues and moves some items around (elastic#55)
5ea9c6d 
* Fixing some grammer issues.  Re ordered parts that I got stuck on that are described later in the readme.

* Just adding some clarity around the number_of_days field.

* Fixing up some syntax and adding back in some examples.

* Fixing some additional typos

* Still more typos.

* Fixed some errors in the markup, and I found my self constantly having to lookup how to pass a particular challenge, so I added that.
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
@costin
quick fix for issue elastic#55
71d05aa
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
@costin
final fix for issue elastic#55
aad9e1f
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
Merged in dev/gideon/sync_to_stack_2021.02.12 (pull request elastic#55)
eec13c5 
* Initial implementation of sync_to_stack

Script to update stack from local code, e.g. to sync to HEAD or master or other
branch.

The script will:
* check and update repos per command line options (currently support one branch
  name for all repos)
* find and classify stack instances
* sync code to engageli and dequeue (recorder/merger) nodes

Approved-by: Matan Yemini
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.06.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @clintongormley