[
https://issues.apache.org/jira/browse/NIFI-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391539#comment-16391539
]
ASF GitHub Bot commented on NIFI-4935:
--------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/2523
NIFI-4935 Support Schema Branches when using HWX Schema Registry
This PR adds optional "Schema Branch" and "Schema Version" properties to
the readers/writers which can be used when using the "Schema Name" access
strategy.
You can specify schema name + branch, or schema name + version, and this
will be passed down to the schema registry implementations. Currently only the
Hortonworks Schema Registry makes use of the branch concept.
This PR also includes some refactoring to clean up the SchemaRegistry
interface and move towards a single method to retrieve a schema that takes a
schema identifier. Also added unit tests for all of the access strategies and
access writers.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi schema-reg-branch
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2523.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2523
----
commit 26b01b6a384cafa50ae262dc9f50e05f41bdb818
Author: Bryan Bende <bbende@...>
Date: 2018-03-05T22:02:20Z
NIFI-4935 Refactoring to support specifying schema branch or schema version
when using schema by name strategy
----
> Support Schema Branches when using HWX Schema Registry
> ------------------------------------------------------
>
> Key: NIFI-4935
> URL: https://issues.apache.org/jira/browse/NIFI-4935
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> The latest version of Hortonworks Schema Registry now supports a
> forking/branching concept. This means that when retrieving a schema by name,
> it may be desirable to also specify a branch name, as the default would
> retrieve from the "master" branch. We'll need to pass down an optional branch
> name to the SchemaRegistry implementations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)