Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/811
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/793
Working on it now.
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/793
@mcgilman, I restored the text and added the class to the div tag. My
canvas is still fixed and the title is back on the Controller Settings page.
Thanks for catching that.
---
If your
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/811
NIFI-2503 Backport PostHTTP SSL Protocol fix to 0.x branch
Merge changes from
[NIFI-1688](https://issues.apache.org/jira/browse/NIFI-1688) /
[PR-624](https://github.com/apache/nifi/pull/624/files
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/806
Extend REST API docs template to handle read only properties.
* Add read only property handling to type.hbs template.
* Add flag to ProcessorDTO.getRelationships to reflect read only nature
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1470
NIFI-3055 StandardRecordWriter Can Throw UTFDataFormatException (0.x)
* Updated StandardRecordWriter to consider the encoding behavior of
java.io.DataOutputStream.writeUTF() and truncate string
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1481
NIFI-3055 StandardRecordWriter Can Throw UTFDataFormatException (0.x)
* Remove function based on JDK source.
* Add new function to find bytes based on RFC3629.
* Add field name to log entry
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1485
NIFI-2890 Provenance Repository Corruption (1.x)
* Corrected handling of corrupt journal file records that prevents instance
startup and loss of records from corrupt files. Specifically, exception
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1484
NIFI-2890 Provenance Repository Corruption (0.x)
* Corrected handling of corrupt journal file records that prevents instance
startup and loss of records from corrupt files. Specifically, exception
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1475
NIFI-3055 StandardRecordWriter Can Throw UTFDataFormatException (1.x)
* Remove function based on JDK source.
* Add new function to find bytes based on RFC3629.
* Add field name to log entry
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1470
Closing this PR, committed on
[4f72e34](https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=4f72e3491f2372c8c45afb96a765c1f5cdd2f07d).
---
If your project is set up for it, you can reply
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1470
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1469
@mosermw I have updated the log message in both PRs. Thanks!
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1201
Replaced by #1484.
---
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
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1203
---
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 user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1201
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1481
Closed by commit
[4f72e34](https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=4f72e3491f2372c8c45afb96a765c1f5cdd2f07d).
Thanks @mosermw!
---
If your project is set up for it, you can
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1481
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1203
Replaced by #1485
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1484
Committed on
[7d23bd7](https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=7d23bd7ac6af228a3e723d18253063231c919cf9).
---
If your project is set up for it, you can reply to this email
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1484
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1128
Closing per commit a3d95dc1582f2edfd7997c5d8a23105e88729d11 by @mosermw .
---
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
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1128
---
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 user jskora closed the pull request at:
https://github.com/apache/nifi/pull/886
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/886
Closed by 0.x branch commit f89bc9efd8b8458b5bfd6a1b4045ce8230117ff4.
Thanks @pvillard31
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/886#discussion_r75469531
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ModifyBytes.java
---
@@ -74,6 +74,13
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/886
@pvillard31, I committed the .allowableValues change to this and the 1.x
pull https://github.com/apache/nifi/pull/890.
---
If your project is set up for it, you can reply to this email and have your
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/904
NIFI-2411 ModifyBytes should use long instead of int for offsets (1.x)
* Update to support offsets larger than 2 gigabyte.
You can merge this pull request into a Git repository by running:
$ git
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/903
NIFI-2411 ModifyBytes should use long instead of int for offsets (0.x)
* Update to support offsets larger than 2 gigabyte.
You can merge this pull request into a Git repository by running:
$ git
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/890
NIFI-1867 Improve ModifyBytes to make it easy to remove all FlowFile
content (1.x)
* Add "Remove All Content" property, related functionality, and tests to
ModifyBytes processor to allo
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/913
@kirkalicious, thanks! The changes look good and tests check out fine.
I'd prefer to move the constants to a parent common to ListFileTransfer and
ListFile, but the only common parent
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/913
@joewitt Thanks, from what I can tell looking at JDK source the format spec
drives the output more than the Locale, so I agree that the comments should
cover it.
@kirkalicious can you add
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1007
NIFI-2752 Correct ReplaceText default pattern and unit tests
* Corrected the DEFAULT_REGEX pattern.
* Added tests to isolate regex capture group problem and verify corrected
functionality
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/913
@kirkalicious Please close this, I committed it, but I transposed the PR
number in the comment.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1072
Reviewing
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1072
Reviewed and committed.
Thanks @mosermw
---
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
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/886
NIFI-1867 Improve ModifyBytes to make it easy to remove all FlowFile
content (0.x)
* Add "Remove All Content" property, related functionality, and tests to
ModifyBytes processor to allo
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1201
NIFI-2890 Provenance Repository Corruption
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1203
NIFI-2890 Provenance Repository Corruption
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following
GitHub user jskora opened a pull request:
https://github.com/apache/nifi-site/pull/7
NIFI-2911 Update Release Guide
* Added steps to configure GPG to default to strong digest algorithms
(SHA512/SHA384/SHA256 over SHA1).
* Added steps to produce SHA-256 checksum over artifacts
GitHub user jskora opened a pull request:
https://github.com/apache/nifi-site/pull/6
NIFI-2910 Added Pony Mail archive links to mailing lists page.
Adds Pony Mail links to the website mailing lists page.
You can merge this pull request into a Git repository by running:
$ git
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1127
@markap14 except for removing the limit, review comments have been
addressed. The FlowFile limit property has been renamed "Max FlowFiles per
Batch" to reflect a batching metaph
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1240
NIFI-3039 Provenance Repository - Fix PurgeOldEvent and Rollover Size
Limits (1.x)
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1241
NIFI-3039 Provenance Repository - Fix PurgeOldEvent and Rollover Size
Limits (0.x)
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1127
NIFI-2861 ControlRate should accept more than one flow file per execution
(1.x)
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1128
NIFI-2861 ControlRate should accept more than one flow file per execution
(0.x)
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1127
@mwoser, I will close and resubmit a clean request with squashed commits.
---
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
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1127
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1412
@mosermw this is the replacement for
https://github.com/apache/nifi/pull/1127, rebased and squashed.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1203
@JPercivall This has @been updated to align with the changes in Apache/0.x.
I couldn't squash without creating a new branch, but a diff with Apache/0.x
only shows the PersistentProvenanceRepository
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1201
@JPercivall this has been updated to align with other changes in Master. I
couldn't squash without creating a new branch, but a diff with Master only
shows the PersistentProvenanceRepository
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1567
NIFI-3517 If HandleHttpResponse cannot write response remove entry from
HttpContextMap
* Add test for failure not clear context map.
* Add handler to remove context map entry if ProcessException
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1994
NIFI-4166 - Create toolkit module to generate and build Swagger API library
for NiFi REST API
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1993
NIFI-3677 - ExtractMediaMetadata should close TikaInputStream
* Added finally block to close TikaInputStream.
Thank you for submitting a contribution to Apache NiFi.
In order
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/2008
NIFI-4183 - Fix handshake error logic in SocketFlowFileServerProtocol
* Added new unit tests to show how the suppressed handshake exceptions
leave the server in a connected status.
* Fixed
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1988#discussion_r125982805
--- Diff:
nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java ---
@@ -756,6 +756,13 @@ public void transfer(FlowFile flowFile
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1986
@trkurc Have you [enabled
SSLv3](https://stackoverflow.com/questions/28236091/how-to-enable-ssl-3-in-java)
in the JVM?
It is disabled by default starting with [Java 8 Update
31](http
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1986
I don't want to complicate this, but I feel like I must be missing
something.
As much as possible, the validation at configuration time should provide
the user feedback, not failure upon
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1666
Reviewing.
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1666
@mwmoser Committed to 0.x on
https://github.com/apache/nifi/commit/5072559156c613823ac554884dd9166acb0edd6b.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1667
Reviewing
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1688
Reviewing
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1699
Reviewing
---
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
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1667
@mosermw Committed on
https://github.com/apache/nifi/commit/cd1cf68c9841d0cc892187ce0e510492cd9ddd48
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1688
Committed on
https://github.com/apache/nifi/commit/b69b3b6c622d27544df70e157f8d8b1531a881c6
and
https://github.com/apache/nifi/commit/c1e65f95bd9951390215c8ef7e2b25cf95f8b5f1
---
If your project
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1699
@mosermw Committed on
https://github.com/apache/nifi/commit/8a18d26c28bcb0e2df6b30359976638637d9.
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1732
NIFI-2752 Correct ReplaceText default pattern and unit tests (0.x)
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/1732
---
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 user jskora commented on the issue:
https://github.com/apache/nifi/pull/1732
@trkurc @pvillard Sorry, my bad for not closing this.
---
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
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/1821
NIFI-3932 Symbols in API comments cause problems with Swagger Codegen
* Update ApiModelProperty descriptions to avoid problematic characters.
Thank you for submitting a contribution to Apache
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/2198
@markap14 I tested on S2S with and without Provenance filter to see the bug
before and after fix and all checked out as expected.
---
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1975
@ijokarumawak @bbende Sorry I haven't kept up with this recently. I'm
happy to say that I was able to do some preliminary testing and this appears to
solve the problem! **_Thanks!_**
ð
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1241
Overcome by events.
---
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1241
@joewitt Since 0.x is end-of-life, this is OBE and should be closed.
IIRC, the root problem was writing records first and then checking
afterward to see if storage limits were exceeded
74 matches
Mail list logo
