[
https://issues.apache.org/jira/browse/NIFIREG-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190272#comment-16190272
]
ASF GitHub Bot commented on NIFIREG-9:
--------------------------------------
Github user bbende commented on a diff in the pull request:
https://github.com/apache/nifi-registry/pull/14#discussion_r142455640
--- Diff:
nifi-registry-framework/src/main/java/org/apache/nifi/registry/service/RegistryService.java
---
@@ -261,6 +262,29 @@ public Bucket deleteBucket(final String
bucketIdentifier) {
}
}
+ public List<BucketItem> getBucketItems(final QueryParameters
queryParameters, final Set<String> bucketIdentifiers) {
+ if (bucketIdentifiers == null || bucketIdentifiers.isEmpty()) {
+ throw new IllegalArgumentException("Bucket Identifiers cannot
be null or empty");
+ }
+
+ readLock.lock();
+ try {
+ final Set<BucketEntity> filterBuckets =
bucketIdentifiers.stream()
--- End diff --
Should we create a method in metadataService to retrieve all the buckets
for the set of ids in one call?
I'm just slightly concerned making an individual DB retrieval for each id
if there are a lot of ids passed in.
> Define web REST API endpoints for user, group, and policy management
> --------------------------------------------------------------------
>
> Key: NIFIREG-9
> URL: https://issues.apache.org/jira/browse/NIFIREG-9
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Fix For: 0.0.1
>
>
> NIFIREG-8 defined web REST API endpoints for domain objects such as buckets
> and flows.
> This ticket scopes work to build on that by adding endpoints for additional
> resources to facilitate user, group, and policy management.
> The interface for user, group, and policy management will be based on the
> NiFi API so as to minimize the effort for NiFi API clients to be reused for
> NiFi Registry.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
