There is no method for sync from CLI in SDK.
I'll add a note in the prefix description about wildcards and regexes
missing support from SDK.
Thanks for the suggestion!
Il giorno mer 13 mar 2024 alle ore 21:13 Andrea Cosentino
ha scritto:
> I'll investigate if there is a way of using sync
I'll investigate if there is a way of using sync somewhat through the sdk.
I'll keep you posted
Il mer 13 mar 2024, 20:47 Mitch Trachtenberg ha scritto:
> My mistake. What I'd thought was just aws cli ls was actually output piped
> through a grep.
>
> Again, though, for many people used to
My mistake. What I'd thought was just aws cli ls was actually output piped
through a grep.
Again, though, for many people used to non-AWS file listings this may come
as a surprise, so it would IMO be helpful to tell people up front that
wildcards, regexes, etc... won't work. And thanks for
Hi,
In the CLI it was escalated but it doesn't seem to be supported:
https://github.com/aws/aws-cli/issues/3784
Usually the CLI/SDK/Rest are aligned, so if it was possible natively
through CLI it would have been possible through SDK.
The prefix is only a String in v1 and v2 and most importantly
Thanks, Claus. I'm sure you're correct and I've looked at the
documentation for ListObjectsRequest.
https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/ListObjectsRequest.html
But it seems like something that is such a common need that it would be
helpful IMO to
Hi
Camel uses the AWS Java SDK and it set the prefix on this SDK so its
depends on if this SDK has any kind of support for wildcards.
As you write its likely it does not have that.
You can try to dive into the AWS SDK and see more deeper.
On Wed, Mar 13, 2024 at 7:19 PM Mitch Trachtenberg
I cannot specifically find this stated in either AWS S3 or Camel
documentation, but it appears that I can give a prefix 1234- to restrict
Camel's (4.3.0) downloads to files starting 1234-, but cannot give a prefix
- to restrict Camel's downloads to files beginning with four characters
and a
Yeah that makes sense. Just wanted to make sure.
So we will have to implement a health monitoring on route level!
Thanks for the clarification!
Regards Christian
Am 13.03.24, 12:50 schrieb "Claus Ibsen" :
Hi
Okay as its a very serious error then its not caught by Camel.
From the javadoc you
And what about my question?
Riccardo
From: Modanese, Riccardo
Date: Monday, 11 March 2024 at 14:14
To: users@camel.apache.org
Subject: Re: Camel-Kafka parameters sanitization
Thanks!
From: Claus Ibsen
Date: Monday, 11 March 2024 at 14:12
To: users@camel.apache.org
Subject: Re: Camel-Kafka
Hi
Okay as its a very serious error then its not caught by Camel.
>From the javadoc you can read
An Error is a subclass of Throwable that indicates serious problems that a
reasonable application should not try to catch. Most such errors are
abnormal conditions. The ThreadDeath error, though a
Hi,
thanks for the repsonse!
Camel 3.22.0
the thrown exception class is:
java.lang.OutOfMemoryError: Java heap space
Regards Christian
Am 13.03.24, 10:16 schrieb "Claus Ibsen" :
What Camel version, and can you tell the exact exception class that was throw
On Tue, Mar 12, 2024 at 2:17 PM
What Camel version, and can you tell the exact exception class that was
throw
On Tue, Mar 12, 2024 at 2:17 PM MÜLLER Christian (ICS460-BAI)
wrote:
> Hello,
>
> we are currently trying to understand the behaviour of camel if a thread
> “crashes” due to heap space.
>
> We observe the following
I try to understand backpressure on Camel routes better. For this purpose,
I set up a load test. This test contains 5 routes that are connected
through direct or seda endpoints. At the end of all routes, I put a delay
or throttle. The routes are getting more messages than the throttle/delay
can
13 matches
Mail list logo
