[jira] [Created] (NIFI-3303) escapeJson in ReplaceText

[tianzk (JIRA)]

tianzk created NIFI-3303:


 Summary: escapeJson in ReplaceText
 Key: NIFI-3303
 URL: https://issues.apache.org/jira/browse/NIFI-3303
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: tianzk
 Attachments: config.png, dataflow.png

I have some problems while using excapeJson and unescapeJson in ReplaceText 
processor.

When I give a string: He didn’t say, “Stop”!  to ReplaceText as input,and 
configure ReplaceText like: attachment config.png

The output of ReplaceText is same with the input: He didn’t say, “Stop!” 
,nothing changed.

As described in NiFI Documentation the output should be: He didn’t say, 
\"Stop!\”.Did I miss something?

Also there are problems with unescapeJson.If input is: He didn’t say, 
\”Sto\\\"p!\”,the return string will be: He didn’t say, ”Sto"p!”.

My dataflow:(GetFile just read a file with a  string as content.)
dataflow.png

Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1101) Processor support Openstack Swift

[Gil Vernik (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810733#comment-15810733
 ] 

Gil Vernik commented on NIFI-1101:
--

Is someone working to extend NiFi with OpenStack Swift API?

> Processor support Openstack Swift
> -
>
> Key: NIFI-1101
> URL: https://issues.apache.org/jira/browse/NIFI-1101
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 0.3.0
>Reporter: robinlin
>Priority: Minor
>
> Hi
> I think the current S3 processors are not available for Openstack Swift.
> So in order to support Openstack Swift functionalities, the following are 
> some processors might have to be implemented
> 1. GetContainer
> 2. PutContainer
> 3. DeleteContainer
> 4. GetSwiftObject
> 5. PutSwiftObject
> 6. DeleteSwiftObject



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1101) Processor support Openstack Swift

[Gil Vernik (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810730#comment-15810730
 ] 

Gil Vernik commented on NIFI-1101:
--

[~jskora], [~robinlin] I am trying to follow the discussion you had in 2015. 
OpenStack Swift and Amazon S3 expose different APIs..different authentication 
methods, etc..  It's not possible to use S3 implementation classes to access 
OpenStack Swift

> Processor support Openstack Swift
> -
>
> Key: NIFI-1101
> URL: https://issues.apache.org/jira/browse/NIFI-1101
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 0.3.0
>Reporter: robinlin
>Priority: Minor
>
> Hi
> I think the current S3 processors are not available for Openstack Swift.
> So in order to support Openstack Swift functionalities, the following are 
> some processors might have to be implemented
> 1. GetContainer
> 2. PutContainer
> 3. DeleteContainer
> 4. GetSwiftObject
> 5. PutSwiftObject
> 6. DeleteSwiftObject



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3302) QueryDatabaseTable incorrectly says it can be triggered by an incoming FlowFile

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810396#comment-15810396
 ] 

ASF GitHub Bot commented on NIFI-3302:
--

GitHub user jfrazee opened a pull request:

https://github.com/apache/nifi/pull/1406

NIFI-3302 QueryDatabaseTable incorrectly says it can be triggered by an 
incoming FlowFile

- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] Is your initial contribution a single, squashed commit?

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [X] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jfrazee/nifi NIFI-3302

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1406.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 #1406


commit b40cbf1ed1298c02ecbb9fb138e18298c281e37d
Author: Joey Frazee 
Date:   2017-01-09T01:44:08Z

NIFI-3302 Remove 'accepts incoming FlowFile' doc from QDT




> QueryDatabaseTable incorrectly says it can be triggered by an incoming 
> FlowFile
> ---
>
> Key: NIFI-3302
> URL: https://issues.apache.org/jira/browse/NIFI-3302
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Joey Frazee
>Priority: Minor
>
> The QueryDatabaseTable documentation annotation incorrectly says "it can be 
> triggered by an incoming FlowFile" despite having an INPUT_FORBIDDEN 
> requirement.
> It looks like this was a cut and paste typo from ExecuteSQL so it just needs 
> to be removed from the doc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3302) QueryDatabaseTable incorrectly says it can be triggered by an incoming FlowFile

[Joey Frazee (JIRA)]

Joey Frazee created NIFI-3302:
-

 Summary: QueryDatabaseTable incorrectly says it can be triggered 
by an incoming FlowFile
 Key: NIFI-3302
 URL: https://issues.apache.org/jira/browse/NIFI-3302
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joey Frazee
Assignee: Joey Frazee
Priority: Minor


The QueryDatabaseTable documentation annotation incorrectly says "it can be 
triggered by an incoming FlowFile" despite having an INPUT_FORBIDDEN 
requirement.

It looks like this was a cut and paste typo from ExecuteSQL so it just needs to 
be removed from the doc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809648#comment-15809648
 ] 

ASF GitHub Bot commented on NIFI-2716:
--

Github user olegz closed the pull request at:

https://github.com/apache/nifi/pull/1118


> Allow NiFi to manage embedded JMS Brokers
> -
>
> Key: NIFI-2716
> URL: https://issues.apache.org/jira/browse/NIFI-2716
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
>
> Several community members expressed interest in NiFi acting as a JMS Broker 
> to avoid deploying and managing external JMS Brokers. While implementing JMS 
> Broker from scratch would be rather complex, using embedded capabilities of 
> some OS JMS Broker implementations (e.g., ActiveMQ) together with native 
> capabilities of  NiFi (i.e., Processor and/or Controller Service) could prove 
> to be a very valuable feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809647#comment-15809647
 ] 

ASF GitHub Bot commented on NIFI-2716:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/1118
  
There seems to be no traction at the moment, closing for now.


> Allow NiFi to manage embedded JMS Brokers
> -
>
> Key: NIFI-2716
> URL: https://issues.apache.org/jira/browse/NIFI-2716
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
>
> Several community members expressed interest in NiFi acting as a JMS Broker 
> to avoid deploying and managing external JMS Brokers. While implementing JMS 
> Broker from scratch would be rather complex, using embedded capabilities of 
> some OS JMS Broker implementations (e.g., ActiveMQ) together with native 
> capabilities of  NiFi (i.e., Processor and/or Controller Service) could prove 
> to be a very valuable feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1118: NIFI-2716 initial implementation of JMS Broker processor

[olegz]

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/1118
  
There seems to be no traction at the moment, closing for now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---