You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Status

Current state: Under Discussion

Discussion thread: https://mail-archives.apache.org/mod_mbox/lucene-dev/202004.mbox/browser

JIRA: Unable to render Jira issues macro, execution error.

Released: 9.0.0

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast). Confluence supports inline comments that can also be used.

Motivation

  1. Improve overall security by removing EOL code from the code base
  2. Preserve functionality by providing an updated Admin UI
  3. Make Solr more approachable by both users and UI devs, while hopefully making it easier to get started with Solr today.

Public Interfaces

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.

Same interface, new look. Existing Solr Admin UI would be removed by the time we are preparing to release 9.0 because we will have reached feature parity. This could happen before we reach 9.0 as well. 

Proposed Changes

Build an Admin UI with the latest version of Angular (9.2.1). Our current version is about five years old.

The new UI will use a module loader and npm to start the app.

The new UI will convert the language to TypeScript as a strongly-typed language fits the Java programmer's paradigm more.

Many of the existing features will improve in terms of accessibility and capabilities. For example, logs will be sortable by every field, searchable, and paginated in the end state.The front page updates will make it easier to discern issues for new users or regular users of the Admin UI.

Compatibility, Deprecation, and Migration Plan

  • Users will be happier.
  • Both UI will exist in parallel for some time until we agree it is time to deprecate and then remove old UI.

Test Plan

The current Admin UI has no automated testing capabilities while the new Admin UI will have basic unit testing capabilities at the component level.

Rejected Alternatives

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.

  • No labels