API abstractions for common operations

[edeandrea]

The langfuse API is very tied to the underlying REST API. We'd like to add a "common functionality" layer that helps with higher level operations.

This discussion is to keep track of such things that may be needed.

[edeandrea]

Things defined in https://github.com/edeandrea/non-deterministic-no-problem/blob/main/src/main/java/ai/scoring/langfuse/init/LangfuseInitializer.java would be nice to have at a higher layer (langfuse api).

[edeandrea]

Opened tracking issue: #91

[edeandrea]

Finding things by name (evaluators, llm connections, etc) and handling pagination would be nice.

[edeandrea]

Opened tracking issue: #92

[edeandrea]

Batch deleting things would be nice, and not just by id. Deleting things by name.

[edeandrea]

Opened tracking issue: #93

[sreelakshmi6903]

LangfuseNotFoundException swallows context — the message is raw JSON like {"message":"Dataset X not found"}; typed fields like getResourceName() would be much easier to work with.

[edeandrea]

Opened tracking issue: #94

[sreelakshmi6903]

Dev Services token expires every 60s and is too short for a manual testing session, and the override resets every time the container restarts; a quarkus.keycloak.devservices.access-token-lifespan property would be nice.

[edeandrea]

This is not related to langfuse. This is a keycloak thing.

[sreelakshmi6903]

It would also be nicer to work with a single dataset existence check, instead of skimming a list of datasets.

[edeandrea]

Opened tracking issue: #95

[sreelakshmi6903]

CreateDatasetItemRequest etc. can't be instantiated directly; you have to use .Builder(), but the compile error just says "protected access" with no hint, is this documented somewhere?

[edeandrea]

CreateDatasetItemRequest has a static builder() method, so you would do

CreateDatasetItemRequest.builder()
    .datasetName("name")
    .build();

All the model objects follow the same behavior.

[edeandrea]

This has been implemented across multiple releases