[jira] [Created] (NIFI-7217) Within the DistributedMapCacheServer, it would be beneficial to more easily purge the entire entry list and specific entries with a particular Cache Entry Identifier
Henry Sowell created NIFI-7217: -- Summary: Within the DistributedMapCacheServer, it would be beneficial to more easily purge the entire entry list and specific entries with a particular Cache Entry Identifier Key: NIFI-7217 URL: https://issues.apache.org/jira/browse/NIFI-7217 Project: Apache NiFi Issue Type: Improvement Reporter: Henry Sowell Currently, I use the DetectDuplicate processor, leveraging the DistributedMapCacheService and DistributedMapCacheServer. I have a flow where we need to periodically reprocess data and need to purge what's stored in the DistributedMapCacheServer. Because our DMCserver was configured to persist cache entries to disk, we are required to manually stop the server, and delete the cache on disk, then restart the server to purge entries. It would be beneficial to be able to more easily purge the entire entry list and specific entries with a specific Cache Entry Identifier. This could be accomplished in a variety of ways (e.g., a button from the controller services menu, within Detect Duplicate processor, etc.). Similar requests have come up from others in the community: https://issues.apache.org/jira/browse/NIFI-4173 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-5171) YandexTranslate Processor Improvement
[
https://issues.apache.org/jira/browse/NIFI-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480797#comment-16480797
]
Henry Sowell commented on NIFI-5171:
I'm copying in the app logs for the Jersey errors this patch also fixes, which
caused the processor to stop working after 1.5.0 came out, so that anyone
encountering similar issues can see what we put together. We fixed the issue by
adding the following dependency to the pom:
{code:java}
//
org.glassfish.jersey.inject
jersey-hk2
${jersey.version}
{code}
nifi-app log (error message):
{code:java}
// 2018-04-17 19:35:57,474 INFO [main] org.apache.nifi.NiFi Launching NiFi...
2018-04-17 19:35:57,829 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader
Determined default nifi.properties path to be
'/opt/nifi/nifi-1.6.0/./conf/nifi.properties'
2018-04-17 19:35:57,832 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader
Loaded 146 properties from /opt/nifi/nifi-1.6.0/./conf/nifi.properties
2018-04-17 19:35:57,838 INFO [main] org.apache.nifi.NiFi Loaded 146 properties
2018-04-17 19:35:57,849 INFO [main] org.apache.nifi.BootstrapListener Started
Bootstrap Listener, Listening for incoming requests on port 37435
2018-04-17 19:35:57,859 INFO [main] org.apache.nifi.BootstrapListener
Successfully initiated communication with Bootstrap
2018-04-17 19:35:57,871 INFO [main] org.apache.nifi.nar.NarUnpacker Expanding
97 NAR files with all processors...
2018-04-17 19:36:11,715 INFO [main] org.apache.nifi.nar.NarUnpacker NAR loading
process took 13843813967 nanoseconds (13 seconds).
2018-04-17 19:36:12,070 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-jetty-bundle-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-jetty-bundle-1.6.0.nar-unpacked]
2018-04-17 19:36:12,078 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/framework/nifi-framework-nar-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/framework/nifi-framework-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,079 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-language-translation-nar-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-language-translation-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,080 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-tcp-nar-1.6.0.nar-unpacked as
class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-tcp-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,081 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-avro-nar-1.6.0.nar-unpacked as
class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-avro-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,082 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-ambari-nar-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-ambari-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,082 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-gcp-services-api-nar-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-gcp-services-api-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,083 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-kerberos-iaa-providers-nar-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-kerberos-iaa-providers-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,084 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-hl7-nar-1.6.0.nar-unpacked as
class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-hl7-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,084 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-spring-nar-1.6.0.nar-unpacked
as class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-spring-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,085 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-snmp-nar-1.6.0.nar-unpacked as
class loader
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-snmp-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,085 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded
NAR file:
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-slack-nar-1.6.0.nar-unpacked as
class loader
org.apach
[jira] [Comment Edited] (NIFI-5171) YandexTranslate Processor Improvement
[ https://issues.apache.org/jira/browse/NIFI-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479406#comment-16479406 ] Henry Sowell edited comment on NIFI-5171 at 5/17/18 5:20 PM: - I created a pull request that adds this functionality. https://github.com/apache/nifi/pull/2715 was (Author: veteranbv): I created a pull request that adds this functionality. > YandexTranslate Processor Improvement > - > > Key: NIFI-5171 > URL: https://issues.apache.org/jira/browse/NIFI-5171 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.6.0 >Reporter: Henry Sowell >Priority: Minor > > I'm currently working to improve the YandexTranslate processor to > automatically detect the input language. Here are the core items to change: > * Default input language blank > * Receive back detected language from API > If default language set, current behavior would remain as-is. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5171) YandexTranslate Processor Improvement
[ https://issues.apache.org/jira/browse/NIFI-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479406#comment-16479406 ] Henry Sowell commented on NIFI-5171: I created a pull request that adds this functionality. > YandexTranslate Processor Improvement > - > > Key: NIFI-5171 > URL: https://issues.apache.org/jira/browse/NIFI-5171 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.6.0 >Reporter: Henry Sowell >Priority: Minor > > I'm currently working to improve the YandexTranslate processor to > automatically detect the input language. Here are the core items to change: > * Default input language blank > * Receive back detected language from API > If default language set, current behavior would remain as-is. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5171) YandexTranslate Processor Improvement
Henry Sowell created NIFI-5171: -- Summary: YandexTranslate Processor Improvement Key: NIFI-5171 URL: https://issues.apache.org/jira/browse/NIFI-5171 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.6.0 Reporter: Henry Sowell I'm currently working to improve the YandexTranslate processor to automatically detect the input language. Here are the core items to change: * Default input language blank * Receive back detected language from API If default language set, current behavior would remain as-is. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4356) GetHTMLElement removes content from resulting flowfiles even when destination is attribute
[
https://issues.apache.org/jira/browse/NIFI-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260245#comment-16260245
]
Henry Sowell commented on NIFI-4356:
+1 on Andy’s proposal. Under the current logic the processor is significantly
handicapped in scenarios where you want to continue working with the original
HTML content. An example would be using HTML elements in attributes for things
like routing the original content based attributes extracted with this
processor.
> GetHTMLElement removes content from resulting flowfiles even when destination
> is attribute
> --
>
> Key: NIFI-4356
> URL: https://issues.apache.org/jira/browse/NIFI-4356
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.3.0
>Reporter: Andy LoPresto
> Labels: html
>
> As noted in
> [StackOverflow|https://stackoverflow.com/questions/46070288/multiple-gethtml-attributes-in-apache-nifi],
> {{GetHTMLElement}} processors cannot be chained because the success
> relationship clears the flowfile content even if the destination is an
> attribute. I propose the logic be changed to the following:
> * Destination = content
> * Replace the flowfile content for the *success* relationship
> * Maintain the content for *original*
> * Destination = attribute
> * Maintain the content for *success* and *original*
> * Add a property descriptor for the attribute name
> * Name attributes {{Attribute.1}} as in {{Extract*}} in the event that
> multiple elements are matched
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
