Skip to content

Feature - Use IRI as the identifier of query #25

@keski

Description

@keski

Is there a reason why continuous queries cannot be identified using as a resource (IRI)? If there is no particular reason for this I would propose making this change in the parse. I've tried this locally and everything seems to work fine. Would this have any unforeseen consequences for the C-SPARQL execution engine?

Example query:

REGISTER STREAM <http://stream2> AS
SELECT *
FROM NAMED STREAM <http://stream1> [RANGE 1s STEP 1s]
WHERE {
   ?s ?p ?o
}

Grammar/master.jj

(t = <SINGLELETTERTEXT> { queryName = queryName + t.image ; } | t = <NUMBERS> { queryName = queryName + t.image ; })+ <SPACE> < AS > { setCsparqlQueryName(queryName.trim()); }

to

( t = <IRIref> <SPACE> < AS > { setCsparqlQueryName(t.image); } )

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions