You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Owen Nichols (JIRA)" <ji...@apache.org> on 2019/04/24 22:23:14 UTC
[jira] [Closed] (GEODE-6340) Add arbitrary key=value metadata to
benchmark runs.
[ https://issues.apache.org/jira/browse/GEODE-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen Nichols closed GEODE-6340.
-------------------------------
> Add arbitrary key=value metadata to benchmark runs.
> ---------------------------------------------------
>
> Key: GEODE-6340
> URL: https://issues.apache.org/jira/browse/GEODE-6340
> Project: Geode
> Issue Type: Improvement
> Components: benchmarks
> Reporter: Helena Bales
> Assignee: Helena Bales
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> User should be able to add arbitrary key=value pair metadata to a benchmark run. The key=value pairs should be stored in the benchmark output in a known location.
> Example (not required implementation):
> ./gradlew benchmark -Phosts=... -PoutputDir=... -Pmetadata=k1=v1,k2=v2
> output/.../metadata.json:
> {
> "k1":"v1",
> "k2":"v2"
> }
> Acceptance:
> Command line option for providing key=value pairs.
> File containing the key=value pairs.
> Arguments can be provide through all helper scripts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)