That's where the search index comes in. You can already use the search API
to find review requests based on those fields, but the API doesn't have
pagination support, and needs a redesign to be useful in that way.
Christian
On Wed, Oct 23, 2019 at 2:41 AM Paul Mansfield <
for searching the description and testing fields, a simple free text
database like namazu would probably be a better way than using SQL to scan
text fields.
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out
Ideally any field in a review request should be useable as a filter, but I
accept that the demands of indexing would be a problem.
On Wednesday, 23 October 2019 08:11:25 UTC+1, Christian Hammond wrote:
>
> So there's a challenge with this that I hadn't considered before.
>
> We don't
So there's a challenge with this that I hadn't considered before.
We don't automatically create an index for the branch field. While we could
push an update that adds one, this can impact upgrades to 3.0.16,
potentially taking a substantially long time to complete. We try to avoid
this for point
Hi Paul,
Hmm, I thought we had this as part of the API. I'll add that for 3.0.16.
We're aiming for an early-November release, trying to wrap up some work
before we get that release ready, but it'll probably be the 5th or the 12th.
If need-be, extensions can always provide custom API to fill in
Hi,
imagine I have some reviews done on a feature branch called "SCRATCH-123",
and I want to search for them using the API.
is this possible?
reading the documents at https://www.reviewboard.org/docs/manual/3.0/webapi/
and
