business-intelligence
Here are 924 public repositories matching this topic...
When the View Query Option is selected, the screen pops up in the middle of the web page and obscures the chart I'm working on. I'd like to be able to move it around so I can see the chart results and the query at the same time. It would be nice to also be able to resize the view query screen to minimize its' presence on the web page. There's a lot of blank space on the right side of the view quer
-
Updated
Aug 13, 2021 - Clojure
-
Updated
Aug 10, 2021 - Python
Describe the bug
If I add one kms key for the entire project that should be used for all models, like below. It will blow up, because you can't add KMS encryption to views. ( Unless I'm missing something here )
models:
test:
+kms_key_name: 'projects/<project>/locations/<location>/keyRings/key-ring/cryptoKeys/key'Steps To Reproduce
Add kms_key_name to the entir
-
Updated
Apr 30, 2021 - JavaScript
-
Updated
Aug 12, 2021 - Java
-
Updated
Aug 2, 2021 - Java
-
Updated
Aug 2, 2021 - JavaScript
-
Updated
Jul 14, 2021 - JavaScript
-
Updated
Jul 20, 2021
-
Updated
Dec 2, 2016 - Python
-
Updated
Jun 24, 2021 - Vue
-
Updated
Jul 23, 2021 - C#
-
Updated
Aug 12, 2021 - JavaScript
-
Updated
Mar 25, 2021
-
Updated
Aug 10, 2021 - Java
-
Updated
Jul 18, 2021 - Java
-
Updated
Jul 7, 2021 - TypeScript
-
Updated
Aug 11, 2021 - TypeScript
-
Updated
Aug 11, 2021 - Python
Is your feature request related to a problem? Please describe.
Job Log 화면 검색조건 내 상태(Running) 의 추가가 필요함
- Canceled를 추가할지에 대해서는 고민이 필요함
-
Updated
Aug 12, 2021 - Java
-
Updated
Aug 3, 2018 - Scala
-
Updated
Aug 11, 2021 - JavaScript
-
Updated
Aug 28, 2019 - Jupyter Notebook
-
Updated
Jun 1, 2021 - Python
-
Updated
Apr 26, 2021 - Java
Improve this page
Add a description, image, and links to the business-intelligence topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the business-intelligence topic, visit your repo's landing page and select "manage topics."

This is kind of a follow up to #32677 and the PR #34762.
In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing:
/api/echo(grafana/tempo#714).