[
https://issues.apache.org/jira/browse/SOLR-14414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928898#comment-17928898
]
Christos Malliaridis commented on SOLR-14414:
---------------------------------------------
I completely agree with your points. An "up-to-date" system is nothing we can
just expect from everyone, especially not in a project that is out there for
many years now. And updating an OS is also not a simple task, as it affects
both devs and CI servers.
My current concern is that NodeJs v16 has reached end of life in 2023,
downgrading doesn't seem like the way to go. And since the next LTS version,
which happens to cause the same issue, is also about to [reach
EOL|https://nodejs.org/en/about/previous-releases#release-schedule], I believe
it is not a bad idea to go with the latest LTS version which is Node 22.
However, your point about disabling the new UI is something we may consider.
{{kotlinNpmInstall}} is a top-level task probably because the Kotlin
Multiplatform plugin is added at project level, even though it is enabled at
module level only. Perhaps it would be different if we would add and configure
it only at module level, but I am not sure if that works.
We would still have to disable the entire UI module, which is possible from
what I know. But we would not have any guarantee about the new stuff that is
being implemented and eventually added in releases. And that also does not
resolve the usage of the EOL node version we are currently using in our project.
I wanted to discuss these topics in the last meetup, but we did not get much
opinions on that, so I am considering a mailing thread next.
> New Admin UI
> ------------
>
> Key: SOLR-14414
> URL: https://issues.apache.org/jira/browse/SOLR-14414
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 9.0
> Reporter: Marcus Eagan
> Priority: Major
> Labels: pull-request-available
> Attachments: QueryUX-SolrAdminUIReboot.mov
>
> Time Spent: 10h
> Remaining Estimate: 0h
>
> We have had a lengthy discussion in the mailing list about the need to build
> a modern UI that is both more security and does not depend on deprecated, end
> of life code. In this ticket, I intend to familiarize the community with the
> efforts of the community to do just that that. While we are nearing feature
> parity, but not there yet as many have suggested we could complete this task
> in iterations, here is an attempt to get the ball rolling. I have mostly
> worked on it in weekend nights on the occasion that I could find the time.
> Angular is certainly not my specialty, and this is my first attempt at using
> TypeScript besides a few brief learning exercises here and there. However, I
> will be engaging experts in both of these areas for consultation as our
> community tries to pull our UI into another era.
> Many of the components here can improve. One or two them need to be
> rewritten, and there are even at least three essential components to the app
> missing, along with some tests. A couple other things missing are the V2 API,
> which I found difficult to build with in this context because it is not
> documented on the web. I understand that it is "self-documenting," but the
> most easy-to-use APIs are still documented on the web. Maybe it is entirely
> documented on the web, and I had trouble finding it. Forgive me, as that
> could be an area of assistance. Another area where I need assistance is
> packaging this application as a Solr package. I understand this app is not in
> the right place for that today, but it can be. There are still many
> improvements to be made in this Jira and certainly in this code.
> The project is located in {{lucene-solr/solr/webapp2}}, where there is a
> README for information on running the app.
> The app can be started from the this directory with {{npm start}} for now. It
> can quickly be modified to start as a part of the typical start commands as
> it approaches parity. I expect there will be a lot of opinions. I welcome
> them, of course. The community input should drive the project's success.
> Discussion in mailing list:
> https://mail-archives.apache.org/mod_mbox/lucene-dev/202004.mbox/%3CCAF76exK-EB_tyFx0B4fBiA%3DJj8gH%3Divn2Uo6cWvMwhvzRdA3KA%40mail.gmail.com%3E
--
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
