[
https://issues.apache.org/jira/browse/CAMEL-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Klug updated CAMEL-19152:
---------------------------------
Description:
a) The datalake component has a createFile operation, which returns a response
of type
DataLakeFileClient, which represents inherently a specific directory. The issue
is that subsequent operations do not make use of that instance, resulting in
the fact that the directory seems to be always root. The proposal is
- to add a new exchange header on createFile, that can be used for further
operations
- if that new exchange header is set for file operations, use the client from
the header
That would allow to seamlessly use createFile, append, ... together while
considering directories.
b) Furthermore, there is an additional flush option on the append operation,
which IMHO might make sense to add
I created the pull request [https://github.com/apache/camel/pull/9532] for
these changes.
was:
a) The datalake component has a createFile operation, which returns a response
of type
DataLakeFileClient, which represents inherently a specific directory. The issue
is that subsequent operations do not make use of that instance, resulting in
the fact that the directory seems to be always root. The proposal is
- to add a new exchange header on createFile, that can be used for further
operations
- if that new exchange header is set for file operations, use the client from
the header
That would allow to seamlessly use createFile, append, ... together while
considering directories.
b) Furthermore, there is an additional flush option on the append operation,
which IMHO might make sense to add
I'm going to create a pull request for that.
> camel-azure - Add file client header and flush option
> -----------------------------------------------------
>
> Key: CAMEL-19152
> URL: https://issues.apache.org/jira/browse/CAMEL-19152
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure
> Affects Versions: 3.20.2
> Reporter: Andreas Klug
> Priority: Trivial
> Fix For: 3.20.3
>
>
> a) The datalake component has a createFile operation, which returns a
> response of type
> DataLakeFileClient, which represents inherently a specific directory. The
> issue is that subsequent operations do not make use of that instance,
> resulting in the fact that the directory seems to be always root. The
> proposal is
> - to add a new exchange header on createFile, that can be used for further
> operations
> - if that new exchange header is set for file operations, use the client
> from the header
> That would allow to seamlessly use createFile, append, ... together while
> considering directories.
> b) Furthermore, there is an additional flush option on the append operation,
> which IMHO might make sense to add
>
> I created the pull request [https://github.com/apache/camel/pull/9532] for
> these changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
