[
https://issues.apache.org/jira/browse/SOLR-16397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697105#comment-17697105
]
Jason Gerlowski commented on SOLR-16397:
----------------------------------------
bq. the Solr tests fail. Not because of my code or my changes but some random
unit tests.
Solr does have a lot of flaky tests unfortunately. Partially this is "by
design", as early in the project's life its developers decided to lean heavily
into randomized certain factors in test suite execution to aggressively flush
out certain types of bugs. But a lot of it is accidental. Regardless of the
cause - it's a pain for sure.
There's been a lot of recent improvement in this area though - I'm a little
surprised you had so much trouble, but I'm sorry to hear it.
I accidentally missed your comment back in February, but I'm still very
interested in seeing this move forward [~aalbahem]. Just saw PR #1349 as well.
Will take a look shortly, sorry for the delay!
> Cosmetic, REST-fulness improvements to v2 "core" APIs
> -----------------------------------------------------
>
> Key: SOLR-16397
> URL: https://issues.apache.org/jira/browse/SOLR-16397
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Affects Versions: main (10.0)
> Reporter: Jason Gerlowski
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As mentioned on SOLR-15781, the v2 API currently has an experimental
> designation, and the community has expressed an interest in using this period
> to update our v2 endpoints to be more REST-ful and consistent. The current
> plan is to follow the specific changes laid out in [this
> spreadsheet|https://docs.google.com/spreadsheets/d/1HAoBBFPpSiT8mJmgNZKkZAPwfCfPvlc08m5jz3fQBpA/edit?usp=sharing],
> though of course nothing there is set in stone and there are still warts to
> be worked out.
> This ticket plans to tackle making the changes required for Solr's "core"
> APIs, as described in the spreadsheet above. ("Core" is a pretty bad
> descriptor but I'm not sure what name to attach to this group. I have in my
> head all of the Solr core/collection APIs that involve adding or operating on
> documents, e.g. {{/select}}, {{/update}}, {{/tag}}, etc.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
