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

Query DSL: Rename filteredQuery to filtered #85

Closed
kimchy opened this issue Mar 23, 2010 · 1 comment
Closed

Query DSL: Rename filteredQuery to filtered #85

kimchy opened this issue Mar 23, 2010 · 1 comment
Labels
>enhancement v0.06.0

Comments

@kimchy
Copy link
Member

kimchy commented Mar 23, 2010

The filteredQuery is badly named, as no other query is suffixed by Query. Rename it to filtered.
@kimchy
Copy link
Member Author

kimchy commented Mar 23, 2010

Query DSL: Rename filteredQuery to filtered, closed by f4c94a3.

dadoonet pushed a commit that referenced this issue Jun 5, 2015
@philwills @dadoonet
Elaborate on how to specify AWS credentials
7af1316 
Closes #85.
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
[test] testSimpleWorkflow() and testListBlobs_26() use same snapshot …
9925604 
…name

`testSimpleWorkflow()` and `testListBlobs_26()` use same `test-snap` snapshot name.

So we might get this issue:

```
2015-04-29 12:02:47,279 WARN  snapshots - [node_s0] failed to create snapshot [test-repo:test-snap]
InvalidSnapshotNameException[[test-repo:test-snap] Invalid snapshot name [test-snap], snapshot with such name already exists]
	at org.elasticsearch.repositories.blobstore.BlobStoreRepository.initializeSnapshot(BlobStoreRepository.java:228)
	at org.elasticsearch.repositories.azure.AzureRepository.initializeSnapshot(AzureRepository.java:148)
	at org.elasticsearch.snapshots.SnapshotsService.beginSnapshot(SnapshotsService.java:303)
	at org.elasticsearch.snapshots.SnapshotsService.access$500(SnapshotsService.java:88)
	at org.elasticsearch.snapshots.SnapshotsService$1$1.run(SnapshotsService.java:229)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
```

Closes #85.
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
@dadoonet
Update to Lucene 4.10.0
888d790 
Closes elastic#85.
@regfaker regfaker mentioned this issue Sep 2, 2019
Closed
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
@dliappis
Follow Rally's Python requirements for the virtualenv (elastic#85)
d4e4af3 
Now that Rally's Python/CI requirements are codified in the Rally repo
under `.ci/`, there's no need to duplicate them in the Makefile.

Use Python requirements defined in the Rally repo to configure the venv
for the rally-eventdata-track as well.
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@danielmitterdorfer
Enable ML release benchmarks
690e793 
With this commit we ensure that ML-related benchmarks can be run for all
release benchmarks starting with Elasticsearch 5.4.0.

Relates elastic#39
Relates elastic#85
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
>enhancement v0.06.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy