Skip to content

Conversation

@gaborbernat
Copy link
Contributor

@gaborbernat gaborbernat commented Oct 2, 2025

Fixes #4740

@oracle-contributor-agreement
Copy link

Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
The following contributors of this PR have not signed the OCA:

To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application.

When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated.

If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Required At least one contributor does not have an approved Oracle Contributor Agreement. label Oct 2, 2025
@vladak
Copy link
Member

vladak commented Oct 14, 2025

The Apirary documentation in the apiary.apib file needs update for the /search endpoint.

@vladak
Copy link
Member

vladak commented Oct 14, 2025

Also, needs a test case.

@vladak
Copy link
Member

vladak commented Oct 14, 2025

Just a note: this conflicts with the changes done for Lucene 9.x update in PR #4867. It looks like this can be reconciled easily, though.

@gaborbernat
Copy link
Contributor Author

I signed the OCA on Friday any idea when it will be approved?

@gaborbernat gaborbernat force-pushed the 4740-feat branch 10 times, most recently from 41ef174 to db9f5fa Compare October 16, 2025 02:39
@gaborbernat gaborbernat requested a review from vladak October 16, 2025 02:39
@gaborbernat gaborbernat force-pushed the 4740-feat branch 3 times, most recently from 35d7af4 to 8fd284e Compare October 16, 2025 14:25
@oracle-contributor-agreement
Copy link

Thank you for signing the OCA.

@oracle-contributor-agreement oracle-contributor-agreement bot added OCA Verified All contributors have signed the Oracle Contributor Agreement. and removed OCA Required At least one contributor does not have an approved Oracle Contributor Agreement. labels Oct 16, 2025
@gaborbernat
Copy link
Contributor Author

@vladak when you can please take another look, thanks!

@vladak
Copy link
Member

vladak commented Oct 21, 2025

@vladak when you can please take another look, thanks!

The failing tests need to be fixed first.

@gaborbernat
Copy link
Contributor Author

@vladak can you take another look please? Thanks!

@vladak
Copy link
Member

vladak commented Nov 14, 2025

In general this looks good; I will go through the test code in a little bit more detail before approving, though.

In the meantime you might want to add copyrights to the changed files.

Signed-off-by: Bernát Gábor <[email protected]>
@gaborbernat gaborbernat force-pushed the 4740-feat branch 4 times, most recently from 3a087ce to 851c7b4 Compare November 17, 2025 15:49
@gaborbernat
Copy link
Contributor Author

gaborbernat commented Nov 17, 2025

In the meantime you might want to add copyrights to the changed files.

Thanks for making the changes, will revisit them soon.

@vladak Not sure I understand what you mean here, but addressed the other feedback.

Take a look at the copyright section in source files with external contributors, for example the file having the biggest count of copyright notices

/*
* Copyright (c) 2005, 2025, Oracle and/or its affiliates. All rights reserved.
* Portions Copyright (c) 2011, Jens Elkner.
* Portions Copyright (c) 2017, 2020, Chris Fraire <[email protected]>.
* Portions Copyright (c) 2019, Krystof Tulinger <[email protected]>.
* Portions Copyright (c) 2023, Ric Harris <[email protected]>.
* Portions Copyright (c) 2024, Gino Augustine <[email protected]>.
*/
While it is not required to add copyright notice I believe, it is a good practice to add it when making non-trivial changes to files (mostly for attribution, I think).

@gaborbernat
Copy link
Contributor Author

@vladak any update this?

@vladak
Copy link
Member

vladak commented Dec 11, 2025

@vladak any update this?

Still need to revisit the changes. In addition to that PR #4867 will create a conflict in SearchEngine.java - need to see what is that best order to merge these, i.e. who will go in first.

Have you made your mind w.r.t. the copyrights yet ?

@vladak vladak mentioned this pull request Dec 11, 2025
Copy link
Member

@vladak vladak left a comment

Choose a reason for hiding this comment

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

Looks good. Needs rebase and merge with the Lucene 9 upgrade changes.

@gaborbernat
Copy link
Contributor Author

Have you made your mind w.r.t. the copyrights yet ?

Not sure what I need to do here 🤔 I'm fine with whatever.

@vladak
Copy link
Member

vladak commented Dec 11, 2025

Have you made your mind w.r.t. the copyrights yet ?

Not sure what I need to do here 🤔 I'm fine with whatever.

I'd say add a copyright entry to each file with a non-trivial change.

@gaborbernat
Copy link
Contributor Author

I'd say add a copyright entry to each file with a non-trivial change.

Do I need to? How would this entry look like?

@vladak
Copy link
Member

vladak commented Dec 11, 2025

I'd say add a copyright entry to each file with a non-trivial change.

Do I need to? How would this entry look like?

I think it is not necessary. Such entry would look like this:

/*
 * ...
 * Portions Copyright (c) 2025, Your Name <[email protected]>.
 */

where the ... stand out for any pre-existing copyright entry. The e-mail is optional. Again, take a look at the example above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Search API allow sort by path

2 participants