Hi Apache Nifi team,
I have a ListS3 processor that works perfectly well on DEV and QA Nifi cluster
but fails in UAT with error: "A HostProvider may not be empty". The processor
configuration is identical between environments.
Interesting point is that it does PutS3 correctly in UAT, but fails
with sequence
of numbers.
Thanks
Natalia
.
-Original Message-
From: Fill, Natalia
Sent: 16 May 2022 13:15
To: dev@nifi.apache.org
Subject: RE: [EXTERNAL] Re: Nifi putting object to S3 directory
Thanks Peter, removing leading slash worked and now Nifi puts file into
specified subdirectory
,
Peter Turcsanyi
On Mon, May 16, 2022 at 12:46 PM Fill, Natalia
wrote:
> Hi Nifi Team,
>
> I am working on a solution to put file into S3 server. I used
> PutS3Object and managed to put some files into a bucket, but it failed
> to put files into specific directories on S3. No erro
Hi Nifi Team,
I am working on a solution to put file into S3 server. I used PutS3Object and
managed to put some files into a bucket, but it failed to put files into
specific directories on S3. No errors, but I don't see the files in the bucket.
I used the following format for object key:
claimName: nificonf-claim
triggers: {}
- apiVersion: v1
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: nificonf-claim
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 1Gi
selector:
matchLabels:
function: ${NAMES
Thu, Feb 13, 2020 at 11:09 AM Fill, Natalia
> wrote:
>
>> Public
>>
>> Hi Shawn,
>> First I tried modifying securityContect first and the familiar error
>> is appeared. I remember trying to run as user 1000 a few days ago and
>> had error similar to below. O
OpenShift only allows range [100047,
100047] then the issue is not resolvable in the current image.
Let me know if you have other views on it.
Thanks
Natalia Fill
Analyst Software Developer
-Original Message-----
From: Fill, Natalia [mailto:natalia.f...@lgim.com]
Sent: 13 February
e: nifi-prov-claim
spec:
accessModes: ["ReadWriteOnce"]
resources:
requests:
storage: 10Gi
- metadata:
name: nifi-state-claim
spec:
accessModes: ["ReadWriteOnce"]
resources:
requests:
anks
Shawn
On 2/12/20, 2:26 PM, "Fill, Natalia" wrote:
Public
Hi Endre,
I certainly agree with the bare metal option. The reason I have a specific
request for OpenShift is the requirement to adhere to organisational
architectural road map.
] https://en.wikipedia.org/wiki/Kaiju
[2] https://en.wikipedia.org/wiki/Pacific_Rim_(film)
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, February 12, 2020 8:14 PM, Fill, Natalia
wrote:
> Public
>
> Hi,
> I am trying to run Nifi pod on OpenShift for
permissions on the volume but I'm not sure
why. Can you share your Kubernetes Yaml file, it will make it easier to track
down the difference? Also what are you using for a persistence volume?
Thanks
Shawn
On 2/12/20, 1:14 PM, "Fill, Natalia" wrote:
Public
Hi,
I am try
Public
Hi,
I am trying to run Nifi pod on OpenShift for several days now and unfortunately
unsuccessfully.
The error that I am getting persistently is
replacing target file /opt/nifi/nifi-current/conf/nifi.properties
sed: couldn't open temporary file /opt/nifi/nifi-current/conf/sedXGg2lo:
12 matches
Mail list logo
