[GitHub] nifi pull request #397: NIFI-1815

Github user jdye64 commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r67618912 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/test/resources/tessdata/tessconfigs/nobatch --- @@ -0,0 +1 @@ + --- End diff

[GitHub] nifi issue #397: NIFI-1815

Github user jdye64 commented on the issue: https://github.com/apache/nifi/pull/397 Olegz any luck getting your local install of Tesseract to work? --- 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

[GitHub] nifi issue #397: NIFI-1815

Github user jdye64 commented on the issue: https://github.com/apache/nifi/pull/397 @olegz my initial intention was that the "TESS_DATA_PATH" and the "TessdataDirectoryValidator" being a required PropertyDescriptor would catch those instances where users tried t

[GitHub] nifi pull request: NIFI-1815

Github user jdye64 commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r64843410 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361

[GitHub] nifi pull request: NIFI-1925: Fixed typo in error message

Github user jdye64 commented on the pull request: https://github.com/apache/nifi/pull/468#issuecomment-221889685 Nice catch Simon. Little things like that are hard to find. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well

[GitHub] nifi pull request: NIFI-1815

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/397 NIFI-1815 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jdye64/nifi NIFI-1815 Alternatively you can review and apply these changes as the patch

[GitHub] nifi pull request: NIFI-1747 add maven-war-plugin to create jar as...

Github user jdye64 commented on the pull request: https://github.com/apache/nifi/pull/340#issuecomment-214313062 @apiri that makes perfect sense to me. Not sure what your preference is but feel free to make the changes yourself if that is easier or let me know if you would like

[GitHub] nifi pull request: NIFI-1805

Github user jdye64 commented on the pull request: https://github.com/apache/nifi/pull/377#issuecomment-213528810 It might make more sense to leave those sort of operations to a ReportingTask however? Does anyone have any thoughts around that? --- If your project is set up

[GitHub] nifi pull request: NIFI-1805

Github user jdye64 commented on the pull request: https://github.com/apache/nifi/pull/377#issuecomment-213528547 @aperepel that isn't a bad idea. That takes a little more discussion around how often we continue to post that bulletin if the threshold is constantly exceeded, what

[GitHub] nifi pull request: NIFI-1805

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/377 NIFI-1805 Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to ConnectionStatus You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] nifi pull request: NIFI-1747 add maven-war-plugin to create jar as...

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/340 NIFI-1747 add maven-war-plugin to create jar as part of the existing … …nifi-web-api build process You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] nifi pull request: NiFi-1356

Github user jdye64 commented on the pull request: https://github.com/apache/nifi/pull/158#issuecomment-171674914 Taking Joe's feedback I merged the two processors InferAvroSchemaFromCSV and InferAvroSchemaFromJSON into a single processor InferAvroSchema. --- If your project is set

[GitHub] nifi pull request: NIFI-1360

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/159 NIFI-1360 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jdye64/nifi NIFI-1360 Alternatively you can review and apply these changes as the patch

[GitHub] nifi pull request: NIFI-1360

Github user jdye64 closed the pull request at: https://github.com/apache/nifi/pull/159 --- 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

[GitHub] nifi pull request: NIFI-1156

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/157 NIFI-1156 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jdye64/nifi NIFI-1356 Alternatively you can review and apply these changes as the patch

[GitHub] nifi pull request: NiFi-1356

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/158 NiFi-1356 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jdye64/nifi NIFI-1356 Alternatively you can review and apply these changes as the patch

[GitHub] nifi pull request: NIFI-1156

Github user jdye64 closed the pull request at: https://github.com/apache/nifi/pull/157 --- 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

[GitHub] nifi pull request: NIFI-1156: HTML Parsing Processors Bundle

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/124 NIFI-1156: HTML Parsing Processors Bundle NIFI-1156: HTML Parsing Processors Bundle. GetHTMLElement, ModifyHTMLElement, and PutHTMLElement You can merge this pull request into a Git repository

[GitHub] nifi pull request: NiFi-1079

GitHub user jdye64 opened a pull request: https://github.com/apache/nifi/pull/109 NiFi-1079 Create a new Attribute from the existing FlowFile attributes by taking either all of the existing attributes or a user defined list. The existing Attributes are converted to JSON