vespa-engine/vespa

Document browser and update interface

Open

#16,876 opened on Mar 10, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (4,948 stars) (561 forks)batch import
good first issue

Description

Find content clusters and schemas using http://localhost:19071/application/v2/tenant/default/session/2/content/services.xml .

Use the schema to auto-generate a form with correct types so valid JSON is generated to PUT/UPDATE/DELETE documents.

Support GET to read one more more documents

Also see #16875

Contributor guide

Tech stack
javarest api
Domain
frontendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Vespa document schemasFamiliarity with Vespa REST APIBasic knowledge of HTTP methods
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Review the Vespa documentation on content clusters and schemas (see issue #16875 for related work). Explore the application/v2 API endpoint at http://localhost:19071/application/v2/tenant/default/session/2/content/services.xml to understand the schema structure. Consider building a simple web interface using Vespa's built in tools or a basic frontend framework. Investigate if there are existing similar components in the Vespa codebase, such as the 'document' API handlers.
Document browser and update interface · vespa-engine/vespa#16876 | Good First Issue