[
https://issues.apache.org/jira/browse/SOLR-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18082694#comment-18082694
]
Jan Høydahl commented on SOLR-18257:
------------------------------------
Hi. I think this was answered on the list as well, but there are two main
reasons:
# The "release" schedule is wildly different. Workloads can be added/modified
without being part of a particular release of the tool itself
# The {{solr-orbit-workloads}} repo uses branches for keeping a workload
compatible with a certain major version of solr. I.e. when running a benchmark
against solr 9 for "geonames" workload, the tool will automatically pull
workload from branch "9", while when running the same workload against solr 10,
it will use the workload on branch "10" etc. This way we can keep a trail of
the same benchmark across an evolution of solr capabilities and APIs.
Other arguments are that this has been the design for both Rally and OSB, so we
need a solid argument to do differently. Those who want to improve the tool
itself contribute to the core repo while those who have developed a new
benchmark for a cool dataset and want to contribute it upstream can do so in
the benchmarks repo.
> Initialize workloads repo
> -------------------------
>
> Key: SOLR-18257
> URL: https://issues.apache.org/jira/browse/SOLR-18257
> Project: Solr
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
>
> The new empty {{solr-orbit-workloads}} repository must be bootstrapped with
> an initial commit.
> I constructed the [https://github.com/janhoy/solr-benchmark-workloads] repo
> from scratch with some files from OSB workloads repo and adapted it. It is
> all committed as the initial commit in the empty repo. We can iterate from
> there with followup commits.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
