Hi Jelle,
I think the StringSeacher tests the regex with partial matching but the TestFilter tests it with entire matching.
Try this expression for the Right Value in the TestFilter.
-----
.*(EXAVB|EXVB|EVAVB).*
-----
In addition, the "Matches Regex" operator seems to always work with case-sensitive mode.
Takashi
Hi Takashi,
thank you for your answer. Following is already sufficient in the TestFilter:
-----
EXAVB|EXVB|EVAVB.*
-----
best regards,
Jelle
Hi @jelle and @takashi
Just to let you know some good news. All of the regex transformers in FME 2016.1 should be working the same way from now on which is as it was working in the StringSearcher. The terminology in regex parameters has been changed to read "Contains Regex". For example if the expression ^a is used it will now match the string abracadabro and @jelle's example will now work as is once the transformer is upgraded.
Hi @jelle and @takashi
Just to let you know some good news. All of the regex transformers in FME 2016.1 should be working the same way from now on which is as it was working in the StringSearcher. The terminology in regex parameters has been changed to read "Contains Regex". For example if the expression ^a is used it will now match the string abracadabro and @jelle's example will now work as is once the transformer is upgraded.
Hi @kenbragg, thanks for the information. I noticed the change just a few days ago, with 2016.1 beta. It's a quiet but definitely great enhancement.
Hi,
@takashi Do you know why the Matches Regex operator is always case-sensitive and if there is a way around this? We got caught out with this since in the Regular Expressions Editor it says it is Case-Insenstive, and is insensitive in the Test String, but for actual transformer it becomes case sensitive!
Thanks
Hi,
@takashi Do you know why the Matches Regex operator is always case-sensitive and if there is a way around this? We got caught out with this since in the Regular Expressions Editor it says it is Case-Insenstive, and is insensitive in the Test String, but for actual transformer it becomes case sensitive!
Thanks
In FME 2016.1, the Matches Regex operator has been replaced with the Contains Regex operator, and the new operator can also be used to determine partial match. It was a good enhancement but the case sensitivity has not changed. As you mentioned, the operator always still works in case-sensitive and there seems to be no option to change the behavior, although the regex editor works in case-insensitive mode.
I already reported to Safe support about the inconsistency between the actual behavior of the operator (case-sensitive) and the regex editor for the operator (case-insensitive), at last March (C113393, PR#69263). It has not been resolved yet in FME 2017 RC :-(
I'm wondering if there is a special reason why they don't fix that. So difficult? > @NatalieAtSafe
Changes in FME 2018 should also make conditional tests more consistent for case sensitivity throughout FME. For example, if you add a Tester in 2018, the Mode option allows you to select the test mode - numeric , case sensitive, case in- sensitive . We also added a date/time mode so you can run conditional tests against the the FME date/times
Hopefully this will help you in future FME projects.
