[jira] [Created] (JENA-1666) Securing TDB dataset with SecurityEvaluator
Vasyl Danyliuk created JENA-1666: Summary: Securing TDB dataset with SecurityEvaluator Key: JENA-1666 URL: https://issues.apache.org/jira/browse/JENA-1666 Project: Apache Jena Issue Type: Question Components: Fuseki, Jena, Permissions, Security, TDB2 Reporter: Vasyl Danyliuk Assignee: Claude Warren Hi guys, Can someone take a look if approach used in [this repository|https://github.com/linked-solutions/fuseki-auth] can be incorporated into Jena Permission project? Also, there is a question on [StackOverflow|https://stackoverflow.com/questions/54268950/how-to-secure-all-newly-created-graphs-in-apache-fuseki-with-securityevaluator] The main idea is to apply SecurityEvaluator to whole dataset instead of one graph. This repository, of course, is not ready to be incorporated just now, but if it's possible in general and does not conflict with the structure/architecture of the project I will refactor it to be more consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1645) Poor performance with full text search (Lucene)
[
https://issues.apache.org/jira/browse/JENA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709812#comment-16709812
]
Vasyl Danyliuk commented on JENA-1645:
--
The query is pretty straightforward:
{code:java}
PREFIX person:
SELECT DISTINCT ?emailId ?content
WHERE {
?person1Id person:name "Person One" .
?person2Id person:name "Second Person" .
{?person1Id email:sent ?emailId . ?person2Id email:received ?emailId .}
UNION
{?person2Id email:sent ?emailId . ?person1Id email:received ?emailId .}
(?emailId ?score ?content) text:query (email:indexedContent "ext to search"
1 "highlight:s: | e:") .
}
{code}
Such cases already covered by tests in jena-text module.
Created pull request with code added to the Lucene index.
> Poor performance with full text search (Lucene)
> ---
>
> Key: JENA-1645
> URL: https://issues.apache.org/jira/browse/JENA-1645
> Project: Apache Jena
> Issue Type: Question
> Components: Jena
>Affects Versions: Jena 3.9.0
>Reporter: Vasyl Danyliuk
>Priority: Major
>
> Situation: half of a million of an indexed by Lucene documents(emails
> actually), searching for emails by sender/receiver and some text.
> If to put text filter in the start of SPARQL query it executes once but in a
> case of very common words here are a lot of results(100 000+) that leads to
> poor performance, limiting results count may and up with missed results.
> If to put text search as the last condition it executes once per each already
> found subject. That's completely OK but text search completely ignores
> subject URI.
> I found two methods in TextQueryPF class: variableSubject(...) for the first
> case, and concreteSubject(...) for the second one.
> The question is: why can't subject URI be used as a constraint in the text
> search?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1645) Poor performance with full text search (Lucene)
[ https://issues.apache.org/jira/browse/JENA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708490#comment-16708490 ] Vasyl Danyliuk commented on JENA-1645: -- I have written some code that uses subject URI as an additional constraint and it works much faster in my case, but not sure if there can be any problems in more general cases. > Poor performance with full text search (Lucene) > --- > > Key: JENA-1645 > URL: https://issues.apache.org/jira/browse/JENA-1645 > Project: Apache Jena > Issue Type: Question > Components: Jena >Affects Versions: Jena 3.9.0 >Reporter: Vasyl Danyliuk >Priority: Major > > Situation: half of a million of an indexed by Lucene documents(emails > actually), searching for emails by sender/receiver and some text. > If to put text filter in the start of SPARQL query it executes once but in a > case of very common words here are a lot of results(100 000+) that leads to > poor performance, limiting results count may and up with missed results. > If to put text search as the last condition it executes once per each already > found subject. That's completely OK but text search completely ignores > subject URI. > I found two methods in TextQueryPF class: variableSubject(...) for the first > case, and concreteSubject(...) for the second one. > The question is: why can't subject URI be used as a constraint in the text > search? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JENA-1645) Poor performance with full text search (Lucene)
Vasyl Danyliuk created JENA-1645: Summary: Poor performance with full text search (Lucene) Key: JENA-1645 URL: https://issues.apache.org/jira/browse/JENA-1645 Project: Apache Jena Issue Type: Question Components: Jena Affects Versions: Jena 3.9.0 Reporter: Vasyl Danyliuk Situation: half of a million of an indexed by Lucene documents(emails actually), searching for emails by sender/receiver and some text. If to put text filter in the start of SPARQL query it executes once but in a case of very common words here are a lot of results(100 000+) that leads to poor performance, limiting results count may and up with missed results. If to put text search as the last condition it executes once per each already found subject. That's completely OK but text search completely ignores subject URI. I found two methods in TextQueryPF class: variableSubject(...) for the first case, and concreteSubject(...) for the second one. The question is: why can't subject URI be used as a constraint in the text search? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
