gmane.comp.apache.uima.devel

[jira] [Resolved] (UIMA-2932) CLI needs to specify how to start a custom service

Burn Lewis (JIRA — 2013-05-23T00:43:19

     [ https://issues.apache.org/jira/browse/UIMA-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Burn Lewis resolved UIMA-2932.
------------------------------

    Resolution: Fixed

Tested with a simple C++ service
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (UIMA-2928) The manifests of the executable jars must be changed when any of its jars change

Burn Lewis (JIRA — 2013-05-23T00:43:20

     [ https://issues.apache.org/jira/browse/UIMA-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Burn Lewis resolved UIMA-2928.
------------------------------

    Resolution: Fixed
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (UIMA-2879) When --all_in_one option set client should not call exit

Burn Lewis (JIRA — 2013-05-23T00:41:20

     [ https://issues.apache.org/jira/browse/UIMA-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Burn Lewis resolved UIMA-2879.
------------------------------

    Resolution: Fixed
    


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2917) Type System Merging for string subtypes with allowed values

Marshall Schor (JIRA — 2013-05-22T21:44:20

    [ https://issues.apache.org/jira/browse/UIMA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664569#comment-13664569 ] 

Marshall Schor commented on UIMA-2917:
--------------------------------------

What happens after this fix, is that an ResourceInitializationException is thrown, saying the 2 same-named types cannot be successfully merged.  

What happened before this fix is that no checking was done, and the "first one" in the merge set "wins", the others were ignored.

To your point of one type system making a restriction, and the other not - let's see... the one not making a restriction would define a feature to be of type "uima.cas.String"; the other would define it to be of type "my.set.of.allowed.values", which, in turn is a subtype of uima.cas.String.

The current merge code requires feature range types to match, in all cases.  So type merging always throws an exception if one feature fff has a range type of uima.cas.String in one definition of type

[jira] [Resolved] (UIMA-2936) DUCC webserver (WS) doesn't handle Custom Service log file correctly

Lou DeGenaro (JIRA — 2013-05-22T20:46:20

     [ https://issues.apache.org/jira/browse/UIMA-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro resolved UIMA-2936.
--------------------------------

    Resolution: Fixed

Code delivered.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (UIMA-2936) DUCC webserver (WS) doesn't handle Custom Service log file correctly

Lou DeGenaro (JIRA — 2013-05-22T20:06:19

Lou DeGenaro created UIMA-2936:
----------------------------------

             Summary: DUCC webserver (WS) doesn't handle Custom Service log file correctly
                 Key: UIMA-2936
                 URL: https://issues.apache.org/jira/browse/UIMA-2936
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 1.0-Ducc


From adjunct complainer:

I've just registered an autostart custom service (121) on the test ducc and it started two POP's 2344 2345 ... but it looks as if the WS assumes all service jobs are UIMA so the WS reports the wrong log filename, e.g. 2345-UIMA-... instead of 2345-POP-...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_init_time_max

Lou DeGenaro (JIRA — 2013-05-22T19:50:19

Lou DeGenaro created UIMA-2935:
----------------------------------

             Summary: DUCC command line interface (CLI) should allow specification of --process_init_time_max
                 Key: UIMA-2935
                 URL: https://issues.apache.org/jira/browse/UIMA-2935
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 1.0-Ducc


1. CLI to support new flag --process_init_time_max <integer>
   a) value to be passed to agent via IDuccStandardInfo
   b) similar to --process_per_item_time_max <integer>  
2. CLI to remove support for --process_get_meta_time_max
   a) get_meta time to be system configruable via ducc.properties

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to normal : UIMA-uimaFIT #61

Apache Jenkins Server — 2013-05-22T19:42:35

See <https://builds.apache.org/job/UIMA-uimaFIT/61/>

[jira] [Resolved] (UIMA-2930) DUCC webserver (WS) should make available button(s) for Job Process (JP) cancellation

Lou DeGenaro (JIRA — 2013-05-22T19:40:21

     [ https://issues.apache.org/jira/browse/UIMA-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro resolved UIMA-2930.
--------------------------------

    Resolution: Fixed

Code delivered.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2930) DUCC webserver (WS) should make available button(s) for Job Process (JP) cancellation

Lou DeGenaro (JIRA — 2013-05-22T19:40:19

    [ https://issues.apache.org/jira/browse/UIMA-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664448#comment-13664448 ] 

Lou DeGenaro commented on UIMA-2930:
------------------------------------

1. Add new "Agent Reason" AdministratorInitiated
2. Insure Job Process Init and Run Times have end time when Job Process is abandoned
3. OR should not overlay Process Deallocation Type if already set
4. Support "confirm relsase shares" in ducc.js
5. New data class JobProcessInfo
6. New WS utilities
   a) to get list of JobId+ProcessId pairs "stuck" on nodes that are not "up"
   b) to determine of request user is an administrator
   c) to build ReleaseMachine and ReleaseAll buttons
7. New WS Servlet to employ ducc_ling to release stuck JPs according to parameter: particular machine or all machines
8. New Hint: Login user is not an Administrator
9. Classic and Scroll views support for Release Stuck JP shares on Machines page by logged-in administrator

[jira] [Resolved] (UIMA-2916) OR should not overlay process PID with null (should a null PID follow in a later Node Inventory report)

Lou DeGenaro (JIRA — 2013-05-22T18:31:22

     [ https://issues.apache.org/jira/browse/UIMA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro resolved UIMA-2916.
--------------------------------

    Resolution: Fixed

Code delivered.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (UIMA-2916) OR should not overlay process PID with null (should a null PID follow in a later Node Inventory report)

Lou DeGenaro (JIRA — 2013-05-22T18:25:20

     [ https://issues.apache.org/jira/browse/UIMA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro reopened UIMA-2916:
--------------------------------


WS should not display JPs that never get assigned PID.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2917) Type System Merging for string subtypes with allowed values

Richard Eckart de Castilho (JIRA — 2013-05-22T16:57:20

    [ https://issues.apache.org/jira/browse/UIMA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664252#comment-13664252 ] 

Richard Eckart de Castilho commented on UIMA-2917:
--------------------------------------------------

It'd be interesting to support the union strategy. It would allow for a kind of "mix-in" strategy. Consider you have one "base" type system which defines a type "Token" with a feature "part-of-speech". Another "tagset" type system would redefine "Token" only allowing "part-of-speech" values from a certain tag set. That would allow to use the inheritance mechanism for something different than specializing for a particular tag set, e.g. to have "Word", "Number" or "Whitespace" sub-types of "Token".

So what happens now in this case? Your definition of "strict" says the values are not merged in a union if the value sets are different. What if one type system does not make a restriction at all and the other does? At least the "closed world" a

[jira] [Closed] (UIMA-2917) Type System Merging for string subtypes with allowed values

Marshall Schor (JIRA — 2013-05-22T15:51:20

     [ https://issues.apache.org/jira/browse/UIMA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor closed UIMA-2917.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.1SDK
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2917) Type System Merging for string subtypes with allowed values

Marshall Schor (JIRA — 2013-05-22T15:01:23

    [ https://issues.apache.org/jira/browse/UIMA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664165#comment-13664165 ] 

Marshall Schor commented on UIMA-2917:
--------------------------------------

The fix (unless others object) will be to implement "strict" merging, so that the closed-universe of possible values will always be as expected.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (UIMA-2934) remove from sorted index broken if FS not in index

Marshall Schor (JIRA — 2013-05-22T14:41:20

     [ https://issues.apache.org/jira/browse/UIMA-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor closed UIMA-2934.
--------------------------------

    Resolution: Fixed
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (UIMA-2934) remove from sorted index broken if FS not in index

Marshall Schor (JIRA — 2013-05-21T21:10:20

Marshall Schor created UIMA-2934:
------------------------------------

             Summary: remove from sorted index broken if FS not in index
                 Key: UIMA-2934
                 URL: https://issues.apache.org/jira/browse/UIMA-2934
             Project: UIMA
          Issue Type: Bug
          Components: Core Java Framework
            Reporter: Marshall Schor
            Assignee: Marshall Schor
             Fix For: 2.4.1SDK


The "improvement" to make remove-from-index work faster on sorted indexes by doing a binary search, is broken - when the element isn't found, it throws an index-array-out-of-bounds exception.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Encouragement for one more vote, please, to release Ruta

Marshall Schor — 2013-05-21T19:11:26

On 5/21/2013 5:39 AM, Richard Eckart de Castilho wrote:
See http://www.apache.org/dev/release.html#approving-a-release and the item
above that.

Basically - download the source release, build according to directions, verify
that it builds OK, and see that it has the proper licenses and notices, has
signatures on jars/zips/tars, verify that the Eclipse update site can be
installed into a (fresh unzip of an) Eclipse IDE, etc.

-Marshall

[jira] [Created] (UIMA-2933) Rute type matcher selects wrong annoation with length 0

Peter Klügl (JIRA — 2013-05-21T17:33:16

Peter Klügl created UIMA-2933:
---------------------------------

             Summary: Rute type matcher selects wrong annoation with length 0
                 Key: UIMA-2933
                 URL: https://issues.apache.org/jira/browse/UIMA-2933
             Project: UIMA
          Issue Type: Bug
          Components: ruta
    Affects Versions: 2.0.1ruta
            Reporter: Peter Klügl
            Assignee: Peter Klügl
             Fix For: 2.0.2ruta


Rute type matcher selects wrong annoation with length 0. It is acutally the correct "next" annotations in the index, but not for the rule element matching.

Armin Wegner reported:
{noformat}
DECLARE Date;
Document{->RETAINTYPE(BREAK, SPACE)};
NUM{REGEXP("\\d\\d")->MARK(Date, 1, 2)} PERIOD;
{noformat}
on the input text
{noformat}
12. Mai 1803
{noformat}
I didn't use SourceDocumentInformation in the rule. I was just in the way. The first token with RutaBasic was NUM(0, 2), that is "12", and the second token was SourceDocumentInformation(0, 0). So the rule

[jira] [Closed] (UIMA-2882) Modify DUCC's Agent to call external script to cleanup rogue processes

Jerry Cwiklik (JIRA — 2013-05-21T17:31:25

     [ https://issues.apache.org/jira/browse/UIMA-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-2882.
-------------------------------

    Resolution: Fixed
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (UIMA-2908) Ducc's AbstractDuccComponent dumps messages to stdout

Jerry Cwiklik (JIRA — 2013-05-21T17:29:18

     [ https://issues.apache.org/jira/browse/UIMA-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-2908.
-------------------------------

    Resolution: Fixed
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira