I have a text file which is not redacting below are the system details and code to reproduce. The text file is inside the zip.
@Test
void scratch() throws Exception {
try (Redactor r = new Redactor(getClass().getResourceAsStream("/50nature.txt"));
OutputStream o = Files.newOutputStream(Paths.get("build/redacted.txt"))) {
Redaction[] redactions =
new Redaction[] { new ExactPhraseRedaction("nature", false, new ReplacementOptions("*")) };
r.apply(redactions);
RasterizationOptions ro = new RasterizationOptions();
ro.setEnabled(false);
r.save(o, ro);
}
}
OS: Windows 11
Java: 17
Redaction SDK: 21.12
50nature.zip (219 Bytes)
@shiva.k
We couldn’t reproduce this issue using latest version of the API. Please take a look at this
output.zip (171 Bytes). We noticed another thing that if the license is not applied, then the output looks different, as in this output.zip (277 Bytes). Could you please try the process again after applying a valid license. You can request a temporary license as well.
I am using an OEM license and have applied license. No watermark content generated when redacted that should mean I have valid license. The first output.zip you shared also have issue the last line is not redacted. Is there an issue in the SDK version I am using?
@shiva.k
Could you please try the latest version of the API?
That is because we tried it without license. You can see second ZIP file with expected output.
Our OEM license do not work in latest versions. Is there any patch for this?
@shiva.k
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): REDACTIONJAVA-243
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
I am able to reproduce this issue in 24.1. The issue can be reproduced if we use all lowercase as search phrase and the file contains different case text.
Please use search phrase as nature not Nature.
@shiva.k
We still cannot reproduce this issue. Please take a look at this screenshot (60.8 KB). Could you please share a screencast, explaining steps to reproduce the issue?