Repository navigation
search using the JFrog CLI takes longer time while running on the larger repository with sort and limit #1374
Closed as not planned
Description
Activity
This issue has been marked as stale due to 6 months of inactivity. As part of our effort to address every issue properly, please feel free to remove the stale label or keep this issue active by leaving a comment. Otherwise, it will be closed in 7 days
This issue was closed due to 7 days of inactivity after being marked as stale. Feel free to reopen it if it remains relevant.
Why was this issue closed without any explanation? Is there a documented workaround to avoid the second query apart from us directly using the
jf apisubcommand?
Problem statement: When we run a search using the JFrog CLI on the larger repository, internally 2 ALQ's will be triggered.
The first AQL is triggered to get the artifact details and the second AQL is to get the properties and pass them to the first AQL to get the artifact details. In a few cases, like if the repository is large then the second AQL takes a longer time to get the properties due to which the overtime of the search is also increased.
Due to a limitation in AQL, properties are not returned as part of the result if the AQL includes sort or limit. The second AQL fetches these properties and adds them to the results of the first AQL.
Expected behaviour: Need to optimize the second AQL query, so that the time taken by it to get the properties will be reduced.