es and you’re using gp3
> EBS volumes, it’s unlikely that multiple content repos will help.
>
> Thanks
> -Mark
>
>
>
>> On Dec 15, 2023, at 3:25 PM, Gregory M. Foreman
>> wrote:
>>
>> Mark:
>>
>> I was just discussing multiple con
Mark:
I was just discussing multiple content repos on EBS volumes with a colleague.
I found your post from a long time ago:
https://lists.apache.org/thread/nq3mpry0wppzrodmldrcfnxwzp3n1cjv
“Re #2: I don't know that i've used any SAN to back my repositories other than
the EBS provided by
to update and test all places where it's
> currently used. The string length limit might not be limited to the
> ObjectMapper either, so that would need checking and working through.
>
> A more centralised configuration might be worthwhile if possible.
>
>
> On Tue, 19
cking and working through.
>
> A more centralised configuration might be worthwhile if possible.
>
>
> On Tue, 19 Sept 2023, 20:42 Gregory M. Foreman,
> mailto:gfore...@spinnerconsulting.com>>
> wrote:
> Defaulting maxStringLength to Integer.MAX_VALUE would be my
rojects/spring-boot/issues/34709#issuecomment-1482939940
>
> <https://github.com/spring-projects/spring-boot/issues/34709#issuecomment-1482939940>
> On Mon, Sep 18, 2023 at 4:23 PM Gregory M. Foreman
> mailto:gfore...@spinnerconsulting.com>>
> wrote:
> Yes
>
> S
version of NiFi are you on?
Thanks
On Mon, Sep 18, 2023 at 11:19 AM Gregory M. Foreman <gfore...@spinnerconsulting.com> wrote:
Hello:
It appears Jackson recently set a 20mb upper boundary on json string field length. Is there a way to remove/override this limit in Nifi?
Thanks,
Greg
Joe:
It is Nifi 1.23.2. The error happens when using JoltTransformJSON on a
flowfile with a string field of >20 mb. The message is output as an error to
nifi-app.log and the bulletin. In this case base64 content is being produced
and added as a json field.
Here is further context:
Hello:
It appears Jackson recently set a 20mb upper boundary on json string field
length. Is there a way to remove/override this limit in Nifi?
Thanks,
Greg
bly best to file a JIRA from here with as much
> detail as you can including the output of 'mvn -version'
>
> Thanks
>
> On Mon, Aug 7, 2023 at 8:59 AM Gregory M. Foreman
> mailto:gfore...@spinnerconsulting.com>>
> wrote:
> Hello:
>
> I am trying to build Nifi 1.
Hello:
I am trying to build Nifi 1.23.0 from source using:
JAVA_OPTS="-Xms128m -Xmx4g"
MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m -Xmx3076m
-XX:MaxPermSize=256m"
mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
but the following error is thrown:
[ERROR]
>
> Does that help?
>
> Thanks
> -Mark
>
>> On Jul 20, 2022, at 9:12 AM, Gregory M. Foreman
>> wrote:
>>
>> Hello:
>>
>> The ExecuteStreamCommand processor has 3 relationships. To trap processing
>> failures, I capture flowf
Hello:
The ExecuteStreamCommand processor has 3 relationships. To trap processing
failures, I capture flowfiles from the original relationship, inspect the cmd
exit status, and reroute to a RetryFlowFile processor if the exit status is not
0. I wanted to see if this could be simplified with
Hello:
My client upgraded to Nifi 1.16.1. With the original flow.xml.gz and
autogenerated flow.json.gz in place everything works fine. When
nifi.flow.configuration.json.file is set to the json file location and the
original nifi.flow.configuration.file is commented out and flow.xml.gz
is something
> that will be addressed as part of regular dependency upgrade reviews.
>
> Regards,
> David Handermann
>
> On Mon, May 2, 2022 at 9:56 AM Gregory M. Foreman
> mailto:gfore...@spinnerconsulting.com>>
> wrote:
> Hello:
>
> Nifi 1.16.1 included upgradin
Hello:
Nifi 1.16.1 included upgrading to zookeeper 3.5.9, which uses log4j 1.2.17
(NIFI-9955). My client currently has an external zookeeper 3.5.8 deployed, it
uses log4j 1.2.17, and it has been flagged to upgrade due to the log4j CVE. I
originally thought that log4j 1.x versions were not
bly itself is done.
> This tends to drift over time as the RPM gets much less attention.
>
> We'll need someone to look into it. If there isn't a JIRA please do file one.
>
> Thanks
>
> On Tue, Dec 21, 2021 at 12:14 PM Gregory M. Foreman
> wrote:
>>
>> I did
are attached.Thanks,Greg
diff
Description: Binary data
On Dec 21, 2021, at 12:16 PM, Gregory M. Foreman <gfore...@spinnerconsulting.com> wrote:Hello Edward:SELinux is running in Permissive mode.GregOn Dec 18, 2021, at 8:15 AM, Edward Armes <edward.ar...@gmail.com> wrote:Hi Greg,Can you conf
>
> On Fri, 17 Dec 2021, 20:55 Gregory M. Foreman,
> mailto:gfore...@spinnerconsulting.com>>
> wrote:
> David:
>
> Correct, only the RPM version. Running nifi.sh start in the regular build
> output directory works fine.
>
> Greg
>
>
>&g
ices
> configured as part of the bootstrap.conf, such as the HTTP notification
> service?
>
> Regards,
> David Handermann
>
> On Fri, Dec 17, 2021 at 1:56 PM Gregory M. Foreman
> mailto:gfore...@spinnerconsulting.com>>
> wrote:
> Hello:
>
> I am having tro
Correction:
> I did note a significant difference between the file contents in the lib
> directories.
> On Dec 17, 2021, at 2:55 PM, Gregory M. Foreman
> wrote:
>
> Hello:
>
> I am having trouble with the Nifi 1.15.1 RPM. The generated code runs when
> exe
tgoing.
>
> It would be helpful to allow for specifying a different SSL Context per
> Remote Process Group, but at this point, it's just not something that's been
> implemented.
>
> Thanks
> -Mark
>
>
> On 2021/09/22 14:56:39, "Gregory M. Foreman"
>
Hello:
I am trying to configure site-to-site on a Nifi 1.12.1 cluster hosted on
Kubernetes.
I would like one TLS cert to be used for communication outside the cluster.
Inbound s2s (cluster acting as s2s server) is handled by an nginx ingress proxy
that presents the cert to clients. No issues
Hello:
I built Nifi 1.12.1 from source and have run into an issue. The
JoltTransformJSON advanced GUI responds with a 500 error:
"An error has occurred loading the editor."
Any suggestions on how to resolve? It is working fine on the docker image with
OpenJDK 11.
Thanks,
Greg
===
Apache
Warm regards,
>
> Jim Williams | Manager, Site Reliability Engineering
>
> jwilli...@alertlogic.com <mailto:jwilli...@alertlogic.com> | alertlogic.com
> <http://alertlogic.com/>
>
>
>
> -Original Message-
> From: Gregory M. Foreman
> Sent: T
Hello:
I am using Nifi 1.11.4 and ran into an issue.
JSON Input:
{
"mac":["aabb"]
}
avro schema defined:
{
"type": "record",
"name": "generalInformation",
"namespace": "org.apache.nifi",
"fields": [
{
"name": "mac",
"type": [
n
> that looks at the value and determines which pattern to use.
>
> Thanks
> -Mark
>
>> On Feb 25, 2021, at 9:35 AM, Gregory M. Foreman
>> wrote:
>>
>> Hello,
>>
>> I am attempting to parse timestamps of various formats/precision within
Hello,
I am attempting to parse timestamps of various formats/precision within the
same field in json. Here is an example (using Nifi 1.11.4):
input:
{"cd": "2021-02-24T12:01:01"}
{"cd": "2021-02-24T12:01:01Z"}
{"cd": "2021-02-25T12:01:01.99"}
{"cd": "2021-02-26T12:01:01.999"}
conversion in
27 matches
Mail list logo
