-
We're starting to see a few performance issues recently, and particularly with the removal of an implicit query (#3323), and the removal of orgs from urls (#3312).
It would be useful to have some q…
-
a feature informally requested by people we talked to at conferences: mark queries to find the code corresponding to slow queries in the query log. If you just add the mark text as a sql comment to th…
cvogt updated
6 years ago
-
My experience with just doing pure BM25 or Hybrid search is good but when I combine these queries with other things like filtering based on nested fields in cross-referenced properties or doing `Aggre…
-
**Is your feature request related to a problem? Please describe.**
We have data sources spanning csv, parquet, etc. but also have a data source using MongoDB. Currently, I have to export our enormous…
-
## Is your feature request related to a problem?
Currently there's no quick way to e.g. count pageviews from users who signed up in the last 7 days. Or count signups from users who did the sign up …
-
A lot of people will probably agree with me when I say there's room for improvement with how we currently log queries.
1. Logging is very noisy because we always print the whole query at INFO. I th…
-
#8194 added the ability to pass URLs with queries around. And when someone else clicks the URL, the query is automatically populated in the sql editor and executed.
The issue here is, it's pretty c…
-
As an operator, I want to be able to access the query tracing stats from the slow query log so that I can quickly diagnose why queries are running slowly.
-
For some reason there are a number of slow queries. Adding items to cart is painfully slow. I'm not entirely sure but from what the query monitor plugin is reporting they seem to be coming from EDD.
-
## Problem Statement
Currently, OpenSearch lacks a direct means of providing insights into “top queries” that have a significant impact on latency and resource usage (including CPU consumption, and…