Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about 'first.core.original_dirname' tag value #384

Open
dearith opened this issue Mar 5, 2021 · 2 comments
Open

Question about 'first.core.original_dirname' tag value #384

dearith opened this issue Mar 5, 2021 · 2 comments

Comments

@dearith
Copy link
Contributor

dearith commented Mar 5, 2021

Hi,

I'm experimenting multiple "incoming" directories in MFDATA with the watched_directories parameter.

If i set watched_directories=incoming,incoming1,incoming2 and I push a file in {{MFMODULE_RUNTIME_HOME}}/var/in/incoming1, the first.core.original_dirname tag value is incoming1. That's OK.

Now if I set watched_directories=incoming,incoming/xxx,incoming2 and I push a file in {{MFMODULE_RUNTIME_HOME}}/var/in/incoming/xxx, the first.core.original_dirname tag value is xxx.
It no longer refers to the incoming subdirectory (something like incoming/xxx or incoming_xxx or ... ). Can you confirm that this is an expected behavior ? Thanks.

@thefab
Copy link
Member

thefab commented Apr 19, 2021

yes this is the current behavior

but I think we could change this to get incoming/xxx instead

@dearith: do you agree with this proposal?

@dearith
Copy link
Contributor Author

dearith commented Apr 19, 2021

@thefab : OK thanks. Yes I agree, but on my mind it's not mandatory : in my use case, the main thing is to know what value I need to check in the value of the tag. Checking "xxx" instead "incoming/xxx" suits me. So I let you decide if this change is necessary or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants