[SERVER-58137] Missing [resolvedViews] field for inserts and commands on time series collections and views Created: 28/Jun/21 Updated: 27/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | George Zhuang (Inactive) | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qi-timeseries, read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Sprint: | Query Execution 2021-07-26, QE 2021-08-09, QE 2021-08-23, QE 2021-09-06, QE 2021-09-20, QE 2021-10-04, QE 2021-10-18, QE 2021-11-01, QE 2021-11-15, QE 2021-11-29, QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-01-24 | ||||||||
| Participants: | |||||||||
| Description |
|
Description In The current issue is that the `resolvedViews` field is not present on all slow query logs including insert and create logs. Example Time Series Insert Log
Example Time Series Create Log
Example View Create Log
|
| Comments |
| Comment by Kyle Suarez [ 01/Feb/22 ] |
|
Sorry for losing track of this ticket – moving back to the QE backlog. |
| Comment by George Zhuang (Inactive) [ 15/Jul/21 ] |
|
kyle.suarez, thanks for the create command suggestion! We can use that. We are attempting to differentiate whether any specific operation is on a timeseries collection, view, or regular collection. Do you have a suggestion for how to differentiate whether an insert operation is on a timeseries collection or regular collection based on the insert slow log (example above in the original description)? This is definitely not a blocker but would be a great low-priority nice-to-have. |
| Comment by Kyle Suarez [ 14/Jul/21 ] |
|
george.zhuang, I just wanted to ping you on the earlier comment. If this is not a blocker, and the information can be gleaned another way, I am inclined to close this as Won't Do. |
| Comment by Kyle Suarez [ 30/Jun/21 ] |
|
| Comment by George Zhuang (Inactive) [ 29/Jun/21 ] |
|
louis.williams, all good to change to an improvement.
kyle.suarez, the InTel team uses slow query logs to populate the visual Profiler. In Profiler, we would like to classify all entries as from a collection, time series collection, or view, and we are unable to without the resolvedViews field. If this requires a large refactor, it is ok for us to only have this classification on queries, but it would be a nice to have on other slow query log lines. |
| Comment by Kyle Suarez [ 28/Jun/21 ] |
|
george.zhuang, I am interested in why you think this field should be present in the two situations you mention. The purpose of us adding resolvedViews is to aid in the debugging of slow queries, and to make sure that a TSE helping a customer debug knows up-front that a namespace is a view. The two cases you've mentioned weren't envisioned as being a use case in
|
| Comment by Louis Williams [ 28/Jun/21 ] |
|
george.zhuang, I've changed this to an Improvement. Is this causing a bug? |