Member since
02-16-2016
176
Posts
197
Kudos Received
17
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3551 | 11-18-2016 08:48 PM | |
6312 | 08-23-2016 04:13 PM | |
1688 | 03-26-2016 12:01 PM | |
1583 | 03-15-2016 12:12 AM | |
16309 | 03-14-2016 10:54 PM |
05-26-2017
08:26 PM
It looks like the Jira is still out there for this issue. Two questions: 1) Where is this on the roadmap to get fixed? and 2) Does this affect all Oracle datatypes, or just the numerics that convert to Java BigDecimal?
... View more
02-14-2019
05:16 AM
can you please upload the sample xml and nifi template here Thanks Nitin
... View more
08-24-2017
03:10 PM
Attached are the logs that are related to my getKafka processor. Can someone please go through the same and let me know what might be going wrong!getkafka-processor-log.txt
... View more
03-28-2016
03:12 PM
1 Kudo
The memory pool names are specific to whatever garbage collector you're using with the JVM. If you're using ParallelGC the choice of names are going to be: PS Eden Space PS Survivor Space PS Old Gen PS Perm Gen For G1GC: G1 Eden G1 Survivor G1 Old Gen G1 Perm Gen And there are others for other garbage collectors. If you're unsure you can connect to a process using jconsole and look at java.lang -> MemoryPool:
... View more
10-10-2018
12:17 PM
@Alex Coast The 5 minute retention of Bulletins is a hard coded value that cannot be edited by the end user. It is normal to see the occasional bulletin from some NiFi processors. For example a failed putSFTP because of filename conflict or network issues, but on retry it is successful. A continuous problem would result in non stop bulletins being produced which would be easily noticed. - Take a look at my response further up on using the "SiteToSiteBulletinReportingTask" if you are looking to retain bulletins info longer, manipulate, route, store that somewhere, etc.. - Thank you, Matt - If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.
... View more
07-15-2019
03:31 PM
the free query form for lastmodified is not correct, because you can manage the updates rows, and also, you will get duplicate rows, so i dont recomend this solution alternative
... View more
07-21-2016
09:03 PM
thanks @jwitt. Was searching for this info.
... View more
04-20-2016
09:22 PM
1 Kudo
Starting 2.2.2, AMS has a new API to discover metrics that can be accessed as: http://<ams-host>:6188/ws/v1/timeline/metrics/metadata Note: These metrics are available to be visualized using Grafana starting 2.2.2
... View more
03-29-2016
06:30 PM
@Andrew Grande To be clear, does HDF 1.1.2.1 also support Kerberized Hbase ?
... View more
03-16-2016
10:13 PM
The NCM in a NiFi cluster typically needs more heap memory. The number of components (processors, input ports, output ports and relationships) x the number of nodes in the NiFi cluster on the graph will drive how much memory your NCM will need. For ~300 - 400 components and 3 - 4 node cluster, the NCM seems pretty good with 8GB of heap. If you encounter heap issue still, you would need to increase the heap size and/or reduce the stat buffer size and/or frequency in the nifi.properties files (NCM and Nodes). nifi.components.status.repository.buffer.size=360 (defaults is 1440) nifi.components.status.snapshot.frequency=5 min (default is 1) This information is accurate as of NiFi 0.5.1 and HDF 1.1.2.
... View more