[jira] [Updated] (UIMA-5954) UIMA-DUCC: The new JP is not generating DD

2019-01-10 Thread Jerry Cwiklik (JIRA)


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

Jerry Cwiklik updated UIMA-5954:

Description: Recent JP refactoring introduced a bug preventing code from 
generating a DD when running in an environment with no shared file system. 
Whats missing is a test for existence of a given DD. The code assumes that the 
DD exists and fails if JP runs on a worker node without shared FS.  (was: The 
recent JP refactoring dropped code responsible for testing if a given DD 
exists. In absence of shared file system, JPs must generate DDs on a local 
machine. The code should first test if DD exists and if this test fails, new DD 
should be generated. This was part of the old JP and due to omission was 
recently dropped. Code effected by this is UimaServiceProcessor)

> UIMA-DUCC: The new JP is not generating DD
> --
>
> Key: UIMA-5954
> URL: https://issues.apache.org/jira/browse/UIMA-5954
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Jerry Cwiklik
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> Recent JP refactoring introduced a bug preventing code from generating a DD 
> when running in an environment with no shared file system. Whats missing is a 
> test for existence of a given DD. The code assumes that the DD exists and 
> fails if JP runs on a worker node without shared FS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (UIMA-5954) UIMA-DUCC: The new JP is not generating DD

2019-01-10 Thread Jerry Cwiklik (JIRA)
Jerry Cwiklik created UIMA-5954:
---

 Summary: UIMA-DUCC: The new JP is not generating DD
 Key: UIMA-5954
 URL: https://issues.apache.org/jira/browse/UIMA-5954
 Project: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
 Fix For: 2.2.3-Ducc


The recent JP refactoring dropped code responsible for testing if a given DD 
exists. In absence of shared file system, JPs must generate DDs on a local 
machine. The code should first test if DD exists and if this test fails, new DD 
should be generated. This was part of the old JP and due to omission was 
recently dropped. Code effected by this is UimaServiceProcessor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (UIMA-5953) UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy is too long

2019-01-10 Thread Jerry Cwiklik (JIRA)


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

Jerry Cwiklik closed UIMA-5953.
---
Resolution: Fixed

Modified to set default timeout to 30 secs

> UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy is too long
> 
>
> Key: UIMA-5953
> URL: https://issues.apache.org/jira/browse/UIMA-5953
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Jerry Cwiklik
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> The DefaultNoTaskAvailableStrategy implements a default strategy for waiting 
> when task is not available. The default waitTime=3. However the code uses 
> the following: 
> waitAwhileCondition.await(waitTime, TimeUnit.SECONDS);
> Change the default timeout to waitTime=30



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (UIMA-5953) UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy is too long

2019-01-10 Thread Jerry Cwiklik (JIRA)


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

Jerry Cwiklik updated UIMA-5953:

Summary: UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy is 
too long  (was: UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy in 
too long)

> UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy is too long
> 
>
> Key: UIMA-5953
> URL: https://issues.apache.org/jira/browse/UIMA-5953
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Jerry Cwiklik
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> The DefaultNoTaskAvailableStrategy implements a default strategy for waiting 
> when task is not available. The default waitTime=3. However the code uses 
> the following: 
> waitAwhileCondition.await(waitTime, TimeUnit.SECONDS);
> Change the default timeout to waitTime=30



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (UIMA-5953) UIMA_DUCC: default timeout in DefaultNoTaskAvailableStrategy in too long

2019-01-10 Thread Jerry Cwiklik (JIRA)
Jerry Cwiklik created UIMA-5953:
---

 Summary: UIMA_DUCC: default timeout in 
DefaultNoTaskAvailableStrategy in too long
 Key: UIMA-5953
 URL: https://issues.apache.org/jira/browse/UIMA-5953
 Project: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
 Fix For: 2.2.3-Ducc


The DefaultNoTaskAvailableStrategy implements a default strategy for waiting 
when task is not available. The default waitTime=3. However the code uses 
the following: 

waitAwhileCondition.await(waitTime, TimeUnit.SECONDS);

Change the default timeout to waitTime=30



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (UIMA-5489) Ruta: verbalization of some elements flawed

2019-01-10 Thread JIRA


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

Peter Klügl resolved UIMA-5489.
---
Resolution: Fixed

> Ruta: verbalization of some elements flawed
> ---
>
> Key: UIMA-5489
> URL: https://issues.apache.org/jira/browse/UIMA-5489
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.0ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> * MATCHEDTEXT
> * contains



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work started] (UIMA-5947) Ruta: regex rule for subtoken annotation fails PARTOF

2019-01-10 Thread JIRA


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

Work on UIMA-5947 started by Peter Klügl.
-
> Ruta: regex rule for subtoken annotation fails PARTOF
> -
>
> Key: UIMA-5947
> URL: https://issues.apache.org/jira/browse/UIMA-5947
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> {noformat}
> PACKAGE uima.ruta.training;
> DECLARE Keyword;
> DECLARE Entity(STRING value);
> DECLARE Digit;
> "11" -> Keyword;
> "[0-9]" -> Digit;
> ADDRETAINTYPE(WS);
> a:(Keyword ANY*{PARTOF({W,Digit})}){-> Entity, Entity.value = a.ct};
> REMOVERETAINTYPE(WS);
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (UIMA-5947) Ruta: regex rule for subtoken annotation fails PARTOF

2019-01-10 Thread JIRA


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

Peter Klügl reassigned UIMA-5947:
-

Assignee: Peter Klügl

> Ruta: regex rule for subtoken annotation fails PARTOF
> -
>
> Key: UIMA-5947
> URL: https://issues.apache.org/jira/browse/UIMA-5947
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> {noformat}
> PACKAGE uima.ruta.training;
> DECLARE Keyword;
> DECLARE Entity(STRING value);
> DECLARE Digit;
> "11" -> Keyword;
> "[0-9]" -> Digit;
> ADDRETAINTYPE(WS);
> a:(Keyword ANY*{PARTOF({W,Digit})}){-> Entity, Entity.value = a.ct};
> REMOVERETAINTYPE(WS);
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (UIMA-5952) Ruta: type namespace prefix for missing script in rules param should be configurable

2019-01-10 Thread JIRA


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

Peter Klügl resolved UIMA-5952.
---
Resolution: Fixed

> Ruta: type namespace prefix for missing script in rules param should be 
> configurable
> 
>
> Key: UIMA-5952
> URL: https://issues.apache.org/jira/browse/UIMA-5952
> Project: UIMA
>  Issue Type: New Feature
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (UIMA-5952) Ruta: type namespace prefix for missing script in rules param should be configurable

2019-01-10 Thread JIRA


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

Peter Klügl reopened UIMA-5952:
---

> Ruta: type namespace prefix for missing script in rules param should be 
> configurable
> 
>
> Key: UIMA-5952
> URL: https://issues.apache.org/jira/browse/UIMA-5952
> Project: UIMA
>  Issue Type: New Feature
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (UIMA-5952) Ruta: type namespace prefix for missing script in rules param should be configurable

2019-01-10 Thread JIRA


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

Peter Klügl resolved UIMA-5952.
---
Resolution: Fixed

> Ruta: type namespace prefix for missing script in rules param should be 
> configurable
> 
>
> Key: UIMA-5952
> URL: https://issues.apache.org/jira/browse/UIMA-5952
> Project: UIMA
>  Issue Type: New Feature
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work started] (UIMA-5952) Ruta: type namespace prefix for missing script in rules param should be configurable

2019-01-10 Thread JIRA


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

Work on UIMA-5952 started by Peter Klügl.
-
> Ruta: type namespace prefix for missing script in rules param should be 
> configurable
> 
>
> Key: UIMA-5952
> URL: https://issues.apache.org/jira/browse/UIMA-5952
> Project: UIMA
>  Issue Type: New Feature
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (UIMA-5881) Ruta: multiple matches of simple wildcard

2019-01-10 Thread JIRA


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

Peter Klügl resolved UIMA-5881.
---
Resolution: Fixed

> Ruta: multiple matches of simple wildcard
> -
>
> Key: UIMA-5881
> URL: https://issues.apache.org/jira/browse/UIMA-5881
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> Ruta: multiple matches of simple wildcard, something like:
> {noformat}
> CW{->A, A};
> # A;
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (UIMA-5951) Ruta: wrong initialization of LazyFeature in stacked feature match

2019-01-10 Thread JIRA


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

Peter Klügl resolved UIMA-5951.
---
Resolution: Fixed

> Ruta: wrong initialization of LazyFeature in stacked feature match
> --
>
> Key: UIMA-5951
> URL: https://issues.apache.org/jira/browse/UIMA-5951
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> parsed initialzed with Measurement:
> {noformat}
> m:Measurement{-> LOG(""+m.ct + ": "+m.unit.parsed)};
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (UIMA-5952) Ruta: type namespace prefix for missing script in rules param should be configurable

2019-01-10 Thread JIRA
Peter Klügl created UIMA-5952:
-

 Summary: Ruta: type namespace prefix for missing script in rules 
param should be configurable
 Key: UIMA-5952
 URL: https://issues.apache.org/jira/browse/UIMA-5952
 Project: UIMA
  Issue Type: New Feature
  Components: Ruta
Affects Versions: 2.6.1ruta
Reporter: Peter Klügl
Assignee: Peter Klügl
 Fix For: 2.7.0ruta






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work started] (UIMA-5489) Ruta: verbalization of some elements flawed

2019-01-10 Thread JIRA


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

Work on UIMA-5489 started by Peter Klügl.
-
> Ruta: verbalization of some elements flawed
> ---
>
> Key: UIMA-5489
> URL: https://issues.apache.org/jira/browse/UIMA-5489
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.0ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> * MATCHEDTEXT
> * contains



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work started] (UIMA-5951) Ruta: wrong initialization of LazyFeature in stacked feature match

2019-01-10 Thread JIRA


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

Work on UIMA-5951 started by Peter Klügl.
-
> Ruta: wrong initialization of LazyFeature in stacked feature match
> --
>
> Key: UIMA-5951
> URL: https://issues.apache.org/jira/browse/UIMA-5951
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> parsed initialzed with Measurement:
> {noformat}
> m:Measurement{-> LOG(""+m.ct + ": "+m.unit.parsed)};
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (UIMA-5951) Ruta: wrong initialization of LazyFeature in stacked feature match

2019-01-10 Thread JIRA
Peter Klügl created UIMA-5951:
-

 Summary: Ruta: wrong initialization of LazyFeature in stacked 
feature match
 Key: UIMA-5951
 URL: https://issues.apache.org/jira/browse/UIMA-5951
 Project: UIMA
  Issue Type: Bug
  Components: Ruta
Affects Versions: 2.6.1ruta
Reporter: Peter Klügl
Assignee: Peter Klügl
 Fix For: 2.7.0ruta


parsed initialzed with Measurement:
{noformat}
m:Measurement{-> LOG(""+m.ct + ": "+m.unit.parsed)};
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (UIMA-5489) Ruta: verbalization of some elements flawed

2019-01-10 Thread JIRA


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

Peter Klügl reopened UIMA-5489:
---

GenericFeatureExpression

> Ruta: verbalization of some elements flawed
> ---
>
> Key: UIMA-5489
> URL: https://issues.apache.org/jira/browse/UIMA-5489
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.0ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.7.0ruta
>
>
> * MATCHEDTEXT
> * contains



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)