[Feature Request] Add partitioning for artifacts
See original GitHub issueIt would be extremely useful if the SDK and WebUI offer support for partitions under the Artifacts
tab.
For example, one could “group” several related artifacts into one collapsible section/partition, removing some clutter from view as needed, etc.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Creating partitioned tables | BigQuery - Google Cloud
Option 2: Click add_box Add field and enter the table schema. Specify each field's Name, Type, and Mode. In the Partition and cluster...
Read more >Pipeline artifacts - GitLab Docs
Propose functionality by submitting a feature request. Join First Look to help shape new features. Feature availability and product trials. View pricing to...
Read more >Add feature flag for dynamic partition overwrite - GitHub
Add new pull requests to Backlog (External). Add feature flag for dynamic partition overwrite #171. Sign in to view logs ... Artifacts –....
Read more >Enforcing Product Partition Interfaces | Android Open Source ...
About the artifact path requirements · Option 1: Include the system module in the makefiles included in oem_system.mk . · Option 2: Install...
Read more >Hierarchical partition keys in Azure Cosmos DB (preview)
With this feature, logical partition key prefixes can exceed 20 GB and 10,000 ... https://mvnrepository.com/artifact/com.azure/azure-cosmos ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s good to know. Unfotunately, this is not an acceptable solution in my use case. There are already multiple lines on each graphs, and it would be unclear which lines to toggle together. Besides, graphs would be very cluttered at first and you’d need to click 20+ lines to hide the ones you don’t want to see. In any case, thanks for your help 😃
Barging in here for a moment, because I think Phillippe will soon run into the same issue I’ve highlighted for the report_single_scalar (though not directly related to this issue).
The current UI reports all said scalars in a single horizontal table. When many scalars are involved, this becomes extremely unusable.
The summary table should be at least pivotable, and ideally allow grouping with a similar concept to title/series.
On Thu, 29 Sep 2022, 19:54 Noam Wasersprung, @.***> wrote: