Hi Marshall,
Thanks for reply.
> In most application scenarios, it is intended that a UIMA pipeline be
> instantiated once, and then reused.
I wanted to know about that.
I will try to post Solr ML.
Thanks!
Jun Ohtani
On 2013/08/29, at 6:23, Marshall Schor wrote:
> This ma
Hi Tommaso,
Thanks for reply.
> which version of Solr are you (and your coworkers) using?
Using Solr 4.4.0.
> as far as I can see it shouldn't differ too much, unless you got evidence
> of that.
Sorry…
I try to write a sample code and get evidence, then I will post result it.
Regards
--
I did some more digging, and found this page:
https://developers.google.com/appengine/docs/java
It has statements about what's allowed, and what's not, and a "Whitelist" of
allowed classes.
https://developers.google.com/appengine/docs/java/jrewhitelist
My guess is that you've perhaps found just
I think this analysis is correct.
UIMA makes use also of the VMID method in the java.rmi... package.
Any chance of getting Google to allow these 2 methods in their App Engine?
I'm wondering if wrapping these in doPriveledged would help - but I think that
depends on how the App engine has set up
This may be a better question for the Solr list. These issues seem to come from
the particular integration of UIMA into SOLR, where it seems to be repeatedly
instantiating new UIMA pipelines, over and over.
In most application scenarios, it is intended that a UIMA pipeline be
instantiated once, a
On 2013-08-28 15:20, Peter Klügl wrote:
Am 28.08.2013 20:33, schrieb Alexandre Patry:
On 2013-08-28 12:19, Peter Klügl wrote:
On 28.08.2013 18:17, Alexandre Patry wrote:
I will be happy to test drive MARKFIRST when it will be in trunk.
It's already in the trunk. If you want, then I can also t
Am 28.08.2013 20:33, schrieb Alexandre Patry:
On 2013-08-28 12:19, Peter Klügl wrote:
On 28.08.2013 18:17, Alexandre Patry wrote:
I will be happy to test drive MARKFIRST when it will be in trunk.
It's already in the trunk. If you want, then I can also think of
something that avoid the visibili
On 2013-08-28 12:19, Peter Klügl wrote:
On 28.08.2013 18:17, Alexandre Patry wrote:
I will be happy to test drive MARKFIRST when it will be in trunk.
It's already in the trunk. If you want, then I can also think of
something that avoid the visibility problem.
I was able to make it work in my ap
On 28.08.2013 18:17, Alexandre Patry wrote:
> On 2013-08-28 11:25, Peter Klügl wrote:
>> On 28.08.2013 16:52, Alexandre Patry wrote:
>>> Hi,
>>>
>>> I use RUTA and I want to delete an annotation if it is within the
>>> first 50 tokens of a document. I came up with the following rules :
>>>
>>>
On 2013-08-28 11:25, Peter Klügl wrote:
On 28.08.2013 16:52, Alexandre Patry wrote:
Hi,
I use RUTA and I want to delete an annotation if it is within the
first 50 tokens of a document. I came up with the following rules :
ANY{POSITION(Document, 1)-> Header};// Annotate the
On 28.08.2013 16:52, Alexandre Patry wrote:
> Hi,
>
> I use RUTA and I want to delete an annotation if it is within the
> first 50 tokens of a document. I came up with the following rules :
>
>ANY{POSITION(Document, 1)-> Header};// Annotate the
>first token in the document
Hi,
I use RUTA and I want to delete an annotation if it is within the first
50 tokens of a document. I came up with the following rules :
ANY{POSITION(Document, 1)-> Header};// Annotate the
first token in the document
Header{->SHIFT(Header, 1, 2)} ANY[0,49];
12 matches
Mail list logo