Skip to content

Conversation

@rpanackal
Copy link
Member

@rpanackal rpanackal commented Jul 29, 2025

Context

AI/ai-sdk-java-backlog#ISSUENUMBER.

This PR carries the changes inapi_hub_merged_spec.yaml in the grounding service PR linked.

Includes:

  1. Support s3 and sftp configuration in MS Sharepoint pipeline creation
  2. Additional fields in pipeline response

Other changes borrowed from some earlier PR, not merged in our main branch spec

  1. Additional endpoint "/pipelines/trigger"
  2. New create pipeline types added SDMPipeline and WorkZone.
  3. Additional fields on DocumentStatus

Feature scope:

  • Client Generation
  • Succesfull compilation
  • Existing unit and e2e test run success
  • Add new tests for the latest features Requires setting up s3 and sftp pipelines

Definition of Done

  • Functionality scope stated & covered
  • Tests cover the scope above
  • Error handling created / updated & covered by the tests above
  • Aligned changes with the JavaScript SDK
  • Documentation updated
  • Release notes updated

@rpanackal rpanackal changed the title chore: [Grounding] Latest spec update check chore: [DevOps] Latest spec update check Jul 30, 2025
newtork
newtork previously approved these changes Aug 1, 2025
Copy link
Contributor

@newtork newtork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

they still do not have version in their spec? FFS

@rpanackal rpanackal changed the title chore: [DevOps] Latest spec update check chore: [DevOps] Latest Grounding spec update check Aug 5, 2025
@rpanackal rpanackal added please-review Request to review a pull-request and removed dont-merge labels Aug 8, 2025
@rpanackal rpanackal self-assigned this Aug 8, 2025
{
@JsonProperty("results")
private List<ResultsInner1> results = new ArrayList<>();
private List<ResultsInner2> results = new ArrayList<>();
Copy link
Contributor

@newtork newtork Aug 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Comment)

Okay we need a follow-up BLI to fix this is in pre-processing with adding/fixing title: FooBar to component schema.
Or we'll tell the maintainers to fix their spec with using unique titles.

* @throws OpenApiRequestException if an error occurs while attempting to invoke the API
*/
@Nonnull
public OpenApiResponse manualTriggerPipeline(
Copy link
Contributor

@newtork newtork Aug 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Question)

We don't have a pipeline integration test right? We may need a BLI if there isn't one already. Low priority.

*/
@Nonnull
public SearchResults search(
public VectorSearchResults search(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Comment)

Also here we may need a BLI for adding an integration test for vector searching. Low priority.

Copy link
Contributor

@newtork newtork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise LGTM, branch looks good according to our process standards.

@rpanackal rpanackal merged commit 5035659 into main Aug 8, 2025
7 checks passed
@rpanackal rpanackal deleted the spec-update/grounding/support-s3-sftp branch August 8, 2025 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

please-review Request to review a pull-request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants