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

ASF GitHub Bot commented on RYA-443:
------------------------------------

Github user ejwhite922 commented on the issue:

    https://github.com/apache/incubator-rya/pull/282
  
    I fixed the issue with `rpm -e` not working with the version number.  The 
plugin's version property was including "-incubating" which RPM's don't like 
"-" in that property.  The version and release properties are appropriate now; 
taken from what the rpm-maven-plugin produces.
    
    The new commit generates an RPM file with a name like:
    
`rya.streams.query-manager-3.2.13-incubating_SNAPSHOT20180404214440-noarch.rpm`
    With `3.2.13` being assigned to the version property and 
`incubating_SNAPSHOT20180404214440` to the release property.
    
    Using `rpm -qa | grep rya` returns:
    `rya.streams.query-manager-3.2.13-incubating_SNAPSHOT20180404214440.noarch`
    
    I confirmed that all the following work for uninstall:
    ```
    sudo yum remove 
rya.streams.query-manager-3.2.13-incubating_SNAPSHOT20180404214440.noarch
    sudo yum remove 
rya.streams.query-manager-3.2.13-incubating_SNAPSHOT20180404214440
    sudo yum remove rya.streams.query-manager-3.2.13
    sudo yum remove rya.streams.query-manager
    sudo rpm -e 
rya.streams.query-manager-3.2.13-incubating_SNAPSHOT20180404214440.noarch
    sudo rpm -e 
rya.streams.query-manager-3.2.13-incubating_SNAPSHOT20180404214440
    sudo rpm -e rya.streams.query-manager-3.2.13
    sudo rpm -e rya.streams.query-manager
    ```


> Implement a single node query manager
> -------------------------------------
>
>                 Key: RYA-443
>                 URL: https://issues.apache.org/jira/browse/RYA-443
>             Project: Rya
>          Issue Type: Task
>            Reporter: Andrew Smith
>            Assignee: Kevin Chilton
>            Priority: Major
>
> We need an application that watches the QueryChangeLog to see when the 
> isActive state of queries changes and then reacts to the state change. If 
> isActive goes to true, the system must start processing the query. If it is 
> false, then it must stop processing the query. This application needs to 
> start when the host machine starts. We plan to support CentOS 7.



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

Reply via email to