[
https://issues.apache.org/jira/browse/SOLR-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794205#comment-17794205
]
Jason Gerlowski commented on SOLR-17100:
----------------------------------------
I wouldn't use the term "rush", but IMO there's value in getting an official
(albeit experimental) release of these clients out there.
Ultimately, I'm skeptical that the feedback we need is going to come with the
current approach. I've been soliciting it for at least 6 months now, without
much success. (see
[JIRA|https://issues.apache.org/jira/browse/SOLR-16835?focusedCommentId=17728970&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17728970],
[Github|https://github.com/apache/solr/pull/1681#issuecomment-1573892626], the
[users list|https://lists.apache.org/thread/tstf1xlyw7xlmfqnv7dtl23s2mlqd2mr],
[conference talks|https://www.youtube.com/watch?v=SOf28pyZVI0], our "virtual
community meetups", etc.).
If we want feedback we need to make accessing these clients as easy and
familiar as possible. We're pretty far from that today. Right now, a user
interested in trying the Python client would have to:
# Find and clone Solr's source code
# Figure out what branch or tag to navigate to based on their Solr version
# Install the prerequisites (e.g. Java) for running the gradle build (which
they may be completely unfamiliar with)
# Run a gradle command to generate the source code they _actually_ care about
# Run a separate Python command to install that code into their environment.
Those steps might not sound intimidating to devs experienced with and invested
in the project. But it's more than enough to turn away anyone with more casual
interest. An official-but-experimental release lets us flatten this all down
to a single "pip install" command and (hopefully) get more feedback as a result.
Is there a reason to _avoid_ publishing these as experimental artifacts?
> Publish generated Python and JS clients
> ---------------------------------------
>
> Key: SOLR-17100
> URL: https://issues.apache.org/jira/browse/SOLR-17100
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: clients - js, clients - python, v2 API
> Reporter: Jason Gerlowski
> Priority: Major
> Labels: V2, client, release
>
> SOLR-16835 and SOLR-17062 gave us the ability to generate Python and
> JavaScript clients from as a part of the Solr build. But while these clients
> are used in small ways for dog-fooding (e.g. in the Admin UI), we aren't yet
> publishing them in any way to make them available to users.
> We should decide on a format for publishing these clients (a source code TGZ,
> pip/npm packages, something else?), and modify our release process to make
> both the JS and Python clients available in that format.
--
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
