usbrandon closed issue #3665: [Feature Request]: DuckDB plugins documentation
improvement
URL: https://github.com/apache/hop/issues/3665
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
usbrandon closed issue #3512: [Bug]: DuckDB- If you send it a Date some kind of
setTimestamp() prepared function fails.
URL: https://github.com/apache/hop/issues/3512
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
usbrandon closed issue #3512: [Bug]: DuckDB- If you send it a Date some kind of
setTimestamp() prepared function fails.
URL: https://github.com/apache/hop/issues/3512
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
usbrandon closed issue #3665: [Feature Request]: DuckDB plugins documentation
improvement
URL: https://github.com/apache/hop/issues/3665
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
usbrandon merged PR #3664:
URL: https://github.com/apache/hop/pull/3664
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
usbrandon closed issue #3510: [Bug]: DuckDB - if a table output fails, the
destination duckdb database file remains locked and can no longer be used.
URL: https://github.com/apache/hop/issues/3510
--
This is an automated message from the Apache Git Service.
To respond to the message, please
usbrandon opened a new issue, #3666:
URL: https://github.com/apache/hop/issues/3666
### Apache Hop version?
2.8-SNAPSHOT
### Java version?
11
### Operating system
Windows
### What happened?
sramazzina commented on PR #3659:
URL: https://github.com/apache/hop/pull/3659#issuecomment-1962103362
I'm sorry I wrote about it on mattermost. I will copy the message here:
_"I made some tests this morning and the delete statement do not throws any
exception if the target file
sramazzina opened a new pull request, #3664:
URL: https://github.com/apache/hop/pull/3664
fix #3510 DuckDB - if a table output fails, the destination duckdb database
file remains locked and can no longer be used.
Thank you for your contribution! Follow
usbrandon merged PR #3663:
URL: https://github.com/apache/hop/pull/3663
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
usbrandon closed issue #3661: [Feature Request]: Enable isSupportsOptionsInURL
in DuckDB database metadata
URL: https://github.com/apache/hop/issues/3661
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
usbrandon merged PR #3662:
URL: https://github.com/apache/hop/pull/3662
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
sramazzina commented on issue #3510:
URL: https://github.com/apache/hop/issues/3510#issuecomment-1961448917
The DuckDB file seems to remain locked only when an exception is raised
during the execution of the table output. I'm trying to understand what's the
difference.
--
This is an
sramazzina commented on issue #3510:
URL: https://github.com/apache/hop/issues/3510#issuecomment-1961276859
My bad, the idea of using transactional run configuration to solve the file
locking problem seems not to be a valuable solution because the problem still
remain. On the other side,
bamaer opened a new pull request, #3663:
URL: https://github.com/apache/hop/pull/3663
**Please** add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly
sramazzina opened a new pull request, #3662:
URL: https://github.com/apache/hop/pull/3662
fix #3661 Enable isSupportsOptionsInURL in DuckDB database metadata
fix #3510 DuckDB - if a table output fails, the destination duckdb database
file remains locked and can no longer be used.
sramazzina commented on issue #3510:
URL: https://github.com/apache/hop/issues/3510#issuecomment-1961169059
Looking at what I detailed in previous message, to have things working we
have 2 options that must be managed:
1) If we want to RW the DuckDB database we must only use a single
17 matches
Mail list logo
