Topic: dictionary values not honored (DC profiler 1.5)
dictionary values not honored (DC profiler 1.5)
I have a varchar column in a mySQL DB that has US zipcodes ( ex : " 77401 "). In my dictionary, I am trying to identify records(rows) that have values like "12345", or "00000"; invalid zipcode values.
However, in this case, the result set for the matches includes ALL values, even when the dictionary file is empty.
I am using DataCleaner 1.5.
Thanks,
Will
However, in this case, the result set for the matches includes ALL values, even when the dictionary file is empty.
I am using DataCleaner 1.5.
Thanks,
Will
Hi Will
I just created a ticket for this issue #289. And looking into it. Can you give me some more information. What datatype are you using for zipcodes i mysql?
/Asbjørn
I just created a ticket for this issue #289. And looking into it. Can you give me some more information. What datatype are you using for zipcodes i mysql?
/Asbjørn
Sorry, i properly should have read your question before answering :). However I have one more question which you hasn't already answered.
Did you match on a subset or on all selected data?
/Asbjørn
Did you match on a subset or on all selected data?
/Asbjørn
Hi, it's simply a varchar (12) with nullable fields.
The dictionary values are just not honored, it's pretty straight forward.
Let me know if you need anything else.
The dictionary values are just not honored, it's pretty straight forward.
Let me know if you need anything else.
I matched on ONLY 1 column named "ZIPCODE"
Does that answer your question ?
Does that answer your question ?
That what I expected as well. This is a bug and I'll be looking into it.
I'll let you know when it is fixed.
I'll let you know when it is fixed.
Thank you very much !
Do you have an estimated time frame ?
Thanks,
Will
Do you have an estimated time frame ?
Thanks,
Will
I found a temporary workaround. If you only selects the column containing the zipcode in the "data selection" tab it seems to work as expected
That did NOT work for me.
Hi guys,
Glad to see that you have been approaching this problem. I'm currently on holiday so I don't have the time to look into it right now, but I will in a few weeks. However, I recall authoring a unittest for this scenario. If you want to investigate further, try looking at this:
Glad to see that you have been approaching this problem. I'm currently on holiday so I don't have the time to look into it right now, but I will in a few weeks. However, I recall authoring a unittest for this scenario. If you want to investigate further, try looking at this:
- TextFileDictionaryTest.java (testNumeric())
Hi infowill,
I finally got to take a look at this and fixed the bug. I was quite surprise to find that this is clearly a bug and there are no apparent workarounds for it except to wait for DC 1.5.2 or use a database-based dictionary. I will try and push for DC 1.5.2 so we can get the fix out soon. For now you can download the latest build from our build and test system.
Best,
Kasper
I finally got to take a look at this and fixed the bug. I was quite surprise to find that this is clearly a bug and there are no apparent workarounds for it except to wait for DC 1.5.2 or use a database-based dictionary. I will try and push for DC 1.5.2 so we can get the fix out soon. For now you can download the latest build from our build and test system.
Best,
Kasper
Log in by clicking the login link at the top of the screen
Go back to forum.
