[
https://issues.apache.org/jira/browse/NIFI-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431542#comment-16431542
]
ASF GitHub Bot commented on NIFI-4914:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2614
@david-streamlio you brought in a whole lot of commits from other people
with that merge from upstream/master. I checked out your branch and did a
rebase on it (`git rebase master`) and that seemed to clear it up. I would
recommend doing that on your branch locally and verifying that that "merge
commit" with the commit message `Merge remote-tracking branch 'upstream/master'
into NIFI-4914` goes away.
As a rule of thumb, this is how you want to do this sort of update:
1. git checkout master
2. git pull upstream master
3. git checkout YOUR_BRANCH
4. git rebase master
Once you've done that, the last command will replay your commits on top of
the most recent version of upstream/master.
> Implement record model processor for Pulsar, i.e. ConsumePulsarRecord,
> PublishPulsarRecord
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-4914
> URL: https://issues.apache.org/jira/browse/NIFI-4914
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.6.0
> Reporter: David Kjerrumgaard
> Priority: Minor
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Create record-based processors for Apache Pulsar
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
