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 to use this processor
Joe,
Please leave the cookie code that I'm reviewing (NIFI-1937) in 0.7.0. I'm
almost done testing.
On Sun, Jun 5, 2016 at 4:13 PM, Joe Witt wrote:
> Team
>
> Several folks have asked for an 070 release. However there are quite a lot
> of tickets hanging out there. I plan
Team
Several folks have asked for an 070 release. However there are quite a lot
of tickets hanging out there. I plan to move them out to allow for a
release to occur. If there are critical items please advise.
Thanks
Joe
On Jun 4, 2016 4:13 PM, "idioma" wrote:
> Joe,
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/397
@olegz definitely was thinking a customValidate check which determined
whether tesseract was ready to roll. If the check you mention does that then
that sounds good. We should be careful about ever
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/397
The DLLs are distributed with the Tesseract JAR, but not _.so_ or other OS
specific libs. Basically the current JAR only supports Windows out-of-the-box.
@joewitt If I understand correctly we need to
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/257
@olegz any luck with this review? Cheers
---
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
GitHub user trixpan opened a pull request:
https://github.com/apache/nifi/pull/496
NIFI-1965 - Implement QueryDNS Processor
* Implement QueryDNS processor
* Create AbstractEnrichProcessor
* Rename nifi-geo-bundle to nifi-enrich-bundle
QueryDNS processor is a