[
https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724663#comment-17724663
]
Mingchun Zhao commented on CONNECTORS-1747:
---
[~kwri...@metacarta.com] Thank you for your
[
https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724654#comment-17724654
]
Karl Wright commented on CONNECTORS-1747:
-
Hi - so just to be clear, what you need to do
[
https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724652#comment-17724652
]
Karl Wright commented on CONNECTORS-1747:
-
[~mingchun.zhao], it will be necessary to also
[
https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright reassigned CONNECTORS-1747:
---
Assignee: Karl Wright
> Add a property to disable logging hop count to
For some reason I did not see any emails from you for a full 10 days after
you sent them. I wonder why this was? Perhaps Apache infrastructure was
misbehaving but I apologize for the late response.
On Sun, May 21, 2023 at 8:59 AM Karl Wright wrote:
> Hi - the big source of bloat for hopcount
Hi - the big source of bloat for hopcount processing is the delete
dependencies table, and the options provided allow you to not track those
at all. The other tables (intrinsiclink and hopcount) are 1:1 with the
documents themselves, so these were not considered worth optimizing.
It may be
Hi Karl,
I am terribly sorry for bothering you while you are busy.
For this issue, I've tried to add a property for disabling hopcount
logging to the database only for jobs with its hopcount mode set to
"keep unreachable documents, forever" in the "Hop Filters" tab.
I would appreciate it if you
