[GitHub] nifi issue #2416: [WIP] NIFI 4774: Provide alternate implementation of Write...

2018-01-19 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2416 while i in no way object to a new implementation, I'm not sure that is the correct solution to the bug described in NIFI-4774[1]. A new implementation would need to be tested to a degree

[GitHub] nifi issue #2461: NIFI-4856 Removed deprecated ByteArrayInputStream referenc...

2018-02-08 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2461 Agreed on specifying a char set, but other than that I think it looks good! ---

[GitHub] nifi issue #2416: NIFI 4774: Provide alternate implementation of Write-Ahead...

2018-02-21 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2416 So, I was under the impression this was still a WIP. I am a HUGE -1 on this change. As @markap14 stated above, this is a critical section of code. And while the previous version has serious flaws

[GitHub] nifi issue #2416: NIFI 4774: Provide alternate implementation of Write-Ahead...

2018-02-21 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2416 I'll grant NIFI-4775 may raise issues with my proposed solution. However, there is a problem right now. My proposed solution addresses the problem right now. Future modification may require

[GitHub] nifi issue #2416: NIFI 4774: Provide alternate implementation of Write-Ahead...

2018-02-21 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2416 I'm glad there's support for making this opt in. One point on @joewitt 's comment : "The claim of a simple fix being available to close the previous gaps doesn't appear to be b

[GitHub] nifi issue #2416: NIFI 4774: Provide alternate implementation of Write-Ahead...

2018-02-21 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2416 Again, I would submit that it isn't violating the data loss guarantees of the original implementation. Yes, some data could potentially be lost, but none that it guaranteed to keep, and in doing so

[GitHub] nifi issue #2416: NIFI 4774: Provide alternate implementation of Write-Ahead...

2018-02-21 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2416 @markap14 yes... under this somewhat unusual circumstance, my proposed solution would sacrifice data for consistency. However, if alwaysSync is set false, there isn't a guarantee of no loss anyway

[GitHub] nifi issue #2284: NIFI-4504, NIFI-4505 added methods to MapCache API …

2017-12-28 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2284 Koji, "Are all of these three methods, removeAndGet, removeByPatternAndGet and keySet required by the folks you know of?" - Yes. "atomicity is not that important

[GitHub] nifi issue #2796: NIFI-5275 PostHTTP SocketConfig setup, fixed connection po...

2018-08-24 Thread devriesb
Github user devriesb commented on the issue: https://github.com/apache/nifi/pull/2796 +1. Looks good, and we've been running the new version successfully for weeks. ---