Is there a crack threshold for MetaTagger 4.1.2?

MetaTagger 4.1.2 (w/ TeamSite 6.7.1)
Solaris 9

Hi folks,

We're upgrading to MetaTagger 4.1.2 from 3.6. In 3.6, there was a default "post-crack-threshold" of 5,000,000 bytes (just shy of 5MB). Is there such a thing in 4.1.2? If so, what is the new threshold, and where can it be tweaked?

I've had no luck in digging through the documentation.

Thanks,

Find more posts tagged with

Comments

nbwoven

"post-crack-threshold" & "total-file-size" were

configurable parameters in metatagger.cfg AFAIK mt-4.x & below.
A default limiting value was put in place because auto-classifying a large document consumes a lot of time and resources .
I haven't checked if this still works in MT-412 & above . I'll keep you posted .

Migrateduser

Dan,

These parameters were eliminated in 4.0 due to the introduction of
a) faster tokenizers (the parse rack command) and b) a multi-threaded server (so that big files didn't block all other clients).

If you want to influence how MT handles input files, there are two options:

a) use the default transconverter and add a pre-processor (see plug-in processors webcast)

b) create a custom transconverter that wraps the standard iwmttransconverter[.exe] but adds exception logic based on size/type/etc.

Let us know if this works for you and which approach you take.
Cheers,
Clark

Migrateduser

Great reply, Clark. Thank you!

I think we're going to leave 4.1.2 as-is. Strangely enough, we were using the ~5 MB limit to enforce good web "netiquette" (i.e., preventing our users from publishing massive files for public consumption).

We were just curious if there was a simple setting to re-apply the threshold. If it becomes a problem, an external task in the workflow will be a better way to enforce this anyway.

Thanks,