[jira] [Created] (RYA-514) Prospector support in Rya shell with Rya-details
David W. Lotts created RYA-514: -- Summary: Prospector support in Rya shell with Rya-details Key: RYA-514 URL: https://issues.apache.org/jira/browse/RYA-514 Project: Rya Issue Type: Improvement Components: clients Environment: shell Reporter: David W. Lotts Currently there does not seem to be a way to install a Rya instance with the prospector active. This should be kind of easy: # Look at extras/indexingExample/src/main/java/ProspectorExample.java # Add to the installer prompts. # Add code where configuration for indexes are used in the shell code. # Also add code where the shell does an installation of new instance of Rya. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (RYA-373) Benchmarks: JMH library cannot be distributed, make optional or replace
[ https://issues.apache.org/jira/browse/RYA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-373. -- > Benchmarks: JMH library cannot be distributed, make optional or replace > --- > > Key: RYA-373 > URL: https://issues.apache.org/jira/browse/RYA-373 > Project: Rya > Issue Type: Task >Affects Versions: 3.2.10 > Environment: We use JMH libraries for benchmark code. JMH uses the > GPL with classpath exception which is explicitly not compatible. > The recommendation is to make a profile so that the benchmark jar it is not > included with the release -or- find a replacement. > (GNU General Public License (GPL), version 2, with the Classpath > exception) JMH Core (org.openjdk.jmh:jmh-core:1.13 - > http://openjdk.java.net/projects/code-tools/jmh/jmh-core/) > (GNU General Public License (GPL), version 2, with the Classpath > exception) JMH Generators: Annotation Processors > (org.openjdk.jmh:jmh-generator-annprocess:1.13 > - http://openjdk.java.net/projects/code-tools/jmh/jmh-generator-annprocess/) >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Major > Fix For: 3.2.12 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RYA-373) Benchmarks: JMH library cannot be distributed, make optional or replace
[ https://issues.apache.org/jira/browse/RYA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts resolved RYA-373. Resolution: Fixed Assignee: David W. Lotts > Benchmarks: JMH library cannot be distributed, make optional or replace > --- > > Key: RYA-373 > URL: https://issues.apache.org/jira/browse/RYA-373 > Project: Rya > Issue Type: Task >Affects Versions: 3.2.10 > Environment: We use JMH libraries for benchmark code. JMH uses the > GPL with classpath exception which is explicitly not compatible. > The recommendation is to make a profile so that the benchmark jar it is not > included with the release -or- find a replacement. > (GNU General Public License (GPL), version 2, with the Classpath > exception) JMH Core (org.openjdk.jmh:jmh-core:1.13 - > http://openjdk.java.net/projects/code-tools/jmh/jmh-core/) > (GNU General Public License (GPL), version 2, with the Classpath > exception) JMH Generators: Annotation Processors > (org.openjdk.jmh:jmh-generator-annprocess:1.13 > - http://openjdk.java.net/projects/code-tools/jmh/jmh-generator-annprocess/) >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Major > Fix For: 3.2.12 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RYA-476) DateTimeWithinPeriodTest is sensitive to DST spring forward.
David W. Lotts created RYA-476: -- Summary: DateTimeWithinPeriodTest is sensitive to DST spring forward. Key: RYA-476 URL: https://issues.apache.org/jira/browse/RYA-476 Project: Rya Issue Type: Test Components: build Affects Versions: 3.2.12 Reporter: David W. Lotts Assignee: David W. Lotts failed assertion here: org.apache.rya.api.functions.DateTimeWithinPeriodTest.testWeeks(DateTimeWithinPeriodTest.java:145) Failed because of DST transition. Test is using the current date and time. Changed to fixed datetime. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RYA-22) MongoDBRyaDAO silently throws exceptions
[
https://issues.apache.org/jira/browse/RYA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts reassigned RYA-22:
-
Assignee: (was: David W. Lotts)
> MongoDBRyaDAO silently throws exceptions
>
>
> Key: RYA-22
> URL: https://issues.apache.org/jira/browse/RYA-22
> Project: Rya
> Issue Type: Bug
> Components: dao
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Priority: Trivial
> Labels: beginner
>
> {{MongoDBRyaDAO}} throws a handful of exceptions during init. These
> exceptions should probably be re-thrown as {{RyaDAOException}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (RYA-412) Implement Mongo RyaClient interactors
[ https://issues.apache.org/jira/browse/RYA-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reassigned RYA-412: -- Assignee: David W. Lotts > Implement Mongo RyaClient interactors > - > > Key: RYA-412 > URL: https://issues.apache.org/jira/browse/RYA-412 > Project: Rya > Issue Type: Sub-task >Affects Versions: 3.2.12 >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Critical > Fix For: 3.2.10 > > > Implement the following interactors for MongoDB, corresponding to the > like-named Accumulo versions that are complete. > Install > GetInstanceDetails > InstanceExists > ListInstances > Uninstall > LoadStatements > LoadStatementsFile > ExecuteSparqlQuery > Also created a factor for constructing an instance of RyaClient.java using > the MongoDB interactors. Update RyaClient to make Accumulo specific > interactors optional. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-412) Implement Mongo RyaClient interactors
David W. Lotts created RYA-412: -- Summary: Implement Mongo RyaClient interactors Key: RYA-412 URL: https://issues.apache.org/jira/browse/RYA-412 Project: Rya Issue Type: Sub-task Affects Versions: 3.2.12 Reporter: David W. Lotts Priority: Critical Implement the following interactors for MongoDB, corresponding to the like-named Accumulo versions that are complete. Install GetInstanceDetails InstanceExists ListInstances Uninstall LoadStatements LoadStatementsFile ExecuteSparqlQuery Also created a factor for constructing an instance of RyaClient.java using the MongoDB interactors. Update RyaClient to make Accumulo specific interactors optional. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (RYA-104) Mongo Support in Rya Administrative Shell
[ https://issues.apache.org/jira/browse/RYA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reopened RYA-104: Assignee: David W. Lotts (was: Kevin Chilton) > Mongo Support in Rya Administrative Shell > - > > Key: RYA-104 > URL: https://issues.apache.org/jira/browse/RYA-104 > Project: Rya > Issue Type: New Feature >Affects Versions: 3.2.9 >Reporter: Andrew Smith >Assignee: David W. Lotts > Fix For: 3.2.10 > > > Implement mongo support for the admin shell. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (RYA-368) Create a Rya Shell for MongoDB
[ https://issues.apache.org/jira/browse/RYA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-368. -- Resolution: Duplicate All work here is merged into the other effort. > Create a Rya Shell for MongoDB > -- > > Key: RYA-368 > URL: https://issues.apache.org/jira/browse/RYA-368 > Project: Rya > Issue Type: Improvement >Reporter: Ray Morcos >Priority: Minor > Fix For: 3.2.12 > > > The Rya Shell will be created for MongoDB. Command functions are shown below. > connect-rya > disconnect-rya > sparql-query-rya > connect-mongo-rya > disconnect-mongo-rya > sparql-query-mongorya > load-rdf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-409) Name search for graduation
David W. Lotts created RYA-409: -- Summary: Name search for graduation Key: RYA-409 URL: https://issues.apache.org/jira/browse/RYA-409 Project: Rya Issue Type: Task Reporter: David W. Lotts Assignee: David W. Lotts Priority: Critical This task is for the portion that the Rya team must do to be sure that the Rya name is not claimed by anyone else with overlaping "goods and services". The steps are detailed here: http://www.apache.org/foundation/marks/naming.html One of the first steps is to create a jira task for the Apache folks that track these things. It will contain all the results of our search. when it is filled out, we turn it over to that Apache team for final approval of our name. It has been created: PODLINGNAMESEARCH-135 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RYA-368) Create a Rya Shell for MongoDB
[ https://issues.apache.org/jira/browse/RYA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255525#comment-16255525 ] David W. Lotts commented on RYA-368: These are probably the same scope > Create a Rya Shell for MongoDB > -- > > Key: RYA-368 > URL: https://issues.apache.org/jira/browse/RYA-368 > Project: Rya > Issue Type: Improvement >Reporter: Ray Morcos >Priority: Minor > Fix For: 3.2.12 > > > The Rya Shell will be created for MongoDB. Command functions are shown below. > connect-rya > disconnect-rya > sparql-query-rya > connect-mongo-rya > disconnect-mongo-rya > sparql-query-mongorya > load-rdf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-384) Vagrant example VM script update to latest version of Rya
David W. Lotts created RYA-384: -- Summary: Vagrant example VM script update to latest version of Rya Key: RYA-384 URL: https://issues.apache.org/jira/browse/RYA-384 Project: Rya Issue Type: Bug Environment: example VM builder Reporter: David W. Lotts Vagrant example VM script pulls pre-built jars and war file from dropbox. The version is 3.2.10 Modify and test with a new version of Rya, as of this writing, about to release: 3.2.11 Also, if possible use prebuild binaries from the Nexus repository. The current prebuilt WAR file probably includes some configuration that would be needed to be added to the Vagrant script. Also there might be some special things done to make it work with the OpenRDF/Seaseme/ Rdf4J Workbench. Aaron did a nice job with that integration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (RYA-317) Implement Nearby for mongo geo
[ https://issues.apache.org/jira/browse/RYA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-317. -- Resolution: Fixed > Implement Nearby for mongo geo > -- > > Key: RYA-317 > URL: https://issues.apache.org/jira/browse/RYA-317 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-317) Implement Nearby for mongo geo
[ https://issues.apache.org/jira/browse/RYA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-317: --- Fix Version/s: 3.2.11 > Implement Nearby for mongo geo > -- > > Key: RYA-317 > URL: https://issues.apache.org/jira/browse/RYA-317 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (RYA-317) Implement Nearby for mongo geo
[ https://issues.apache.org/jira/browse/RYA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reopened RYA-317: Need to update the fix version > Implement Nearby for mongo geo > -- > > Key: RYA-317 > URL: https://issues.apache.org/jira/browse/RYA-317 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (RYA-267) Free text indexing fails to flush writes for non-mock.
[ https://issues.apache.org/jira/browse/RYA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts resolved RYA-267. Resolution: Fixed Fix Version/s: 3.2.11 This was resolved along with the commits for RYA-266. I saw that the entity index had a similar fix already in place. > Free text indexing fails to flush writes for non-mock. > -- > > Key: RYA-267 > URL: https://issues.apache.org/jira/browse/RYA-267 > Project: Rya > Issue Type: Sub-task > Components: dao, sail >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: accumulo, free-text, index > Fix For: 3.2.11 > > > This is not confirmed, but it works exactly the way temporal indexing > work(ed) and so will probably fail the same way. > Free text indexing probably writes nothing to it's tables. > It probably does work for a mock instance. It might also work for a large > ingest since it would force a flush. > See the parent RYA-72 for an explanation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (RYA-267) Free text indexing fails to flush writes for non-mock.
[ https://issues.apache.org/jira/browse/RYA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reassigned RYA-267: -- Assignee: David W. Lotts > Free text indexing fails to flush writes for non-mock. > -- > > Key: RYA-267 > URL: https://issues.apache.org/jira/browse/RYA-267 > Project: Rya > Issue Type: Sub-task > Components: dao, sail >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: accumulo, free-text, index > > This is not confirmed, but it works exactly the way temporal indexing > work(ed) and so will probably fail the same way. > Free text indexing probably writes nothing to it's tables. > It probably does work for a mock instance. It might also work for a large > ingest since it would force a flush. > See the parent RYA-72 for an explanation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (RYA-266) Temporal index fails to write when using non-mock accumulo
[ https://issues.apache.org/jira/browse/RYA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-266. -- Resolution: Fixed Fix Version/s: 3.2.11 This also covered the same issue with FreeText search. > Temporal index fails to write when using non-mock accumulo > -- > > Key: RYA-266 > URL: https://issues.apache.org/jira/browse/RYA-266 > Project: Rya > Issue Type: Sub-task > Components: dao, sail > Environment: indexing >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: flush, index, temporal > Fix For: 3.2.11 > > Original Estimate: 24h > Remaining Estimate: 24h > > Temporal indexing writes nothing to it's table name: [prefix]temporal. > It does seem to work for a mock instance. It might also work for a large > ingest since it would force a flush. > See the parent RYA-72 for an explanation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (RYA-372) Replace org.json:json library with a compatibly licensed alternative
[ https://issues.apache.org/jira/browse/RYA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reassigned RYA-372: -- Assignee: David W. Lotts > Replace org.json:json library with a compatibly licensed alternative > > > Key: RYA-372 > URL: https://issues.apache.org/jira/browse/RYA-372 > Project: Rya > Issue Type: Task >Affects Versions: 3.2.10 >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Minor > Fix For: 3.2.12 > > > the JSON library that we use is not compatible and should be replaced. > As of 2016-11-03 this has been moved to the 'Category X' license list > "The Software shall be used for Good, not Evil." from > http://www.json.org/license.html > Consider replacing with this drop in replacement: > https://mvnrepository.com/artifact/com.tdunning/json > from: https://stackoverflow.com/questions/10396176/org-json-jar-provisioning > other alternatives: > https://wiki.debian.org/qa.debian.org/jsonevil > (provided without support or warranty) JSON (JavaScript Object Notation) > (org.json:json:20090211 - http://www.json.org/java/index.html) > See 36 other apache projects that have done this: > https://issues.apache.org/jira/issues/?jql=text%20~%20%22JSON%20EVIL%22 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-373) Benchmarks: JMH library cannot be distributed, make optional or replace
David W. Lotts created RYA-373: -- Summary: Benchmarks: JMH library cannot be distributed, make optional or replace Key: RYA-373 URL: https://issues.apache.org/jira/browse/RYA-373 Project: Rya Issue Type: Task Affects Versions: 3.2.10 Environment: We use JMH libraries for benchmark code. JMH uses the GPL with classpath exception which is explicitly not compatible. The recommendation is to make a profile so that the benchmark jar it is not included with the release -or- find a replacement. (GNU General Public License (GPL), version 2, with the Classpath exception) JMH Core (org.openjdk.jmh:jmh-core:1.13 - http://openjdk.java.net/projects/code-tools/jmh/jmh-core/) (GNU General Public License (GPL), version 2, with the Classpath exception) JMH Generators: Annotation Processors (org.openjdk.jmh:jmh-generator-annprocess:1.13 - http://openjdk.java.net/projects/code-tools/jmh/jmh-generator-annprocess/) Reporter: David W. Lotts Fix For: 3.2.12 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-372) Replace org.json:json library with a compatibly licensed alternative
David W. Lotts created RYA-372: -- Summary: Replace org.json:json library with a compatibly licensed alternative Key: RYA-372 URL: https://issues.apache.org/jira/browse/RYA-372 Project: Rya Issue Type: Task Affects Versions: 3.2.10 Reporter: David W. Lotts Priority: Minor Fix For: 3.2.12 the JSON library that we use is not compatible and should be replaced. As of 2016-11-03 this has been moved to the 'Category X' license list "The Software shall be used for Good, not Evil." from http://www.json.org/license.html Consider replacing with this drop in replacement: https://mvnrepository.com/artifact/com.tdunning/json from: https://stackoverflow.com/questions/10396176/org-json-jar-provisioning other alternatives: https://wiki.debian.org/qa.debian.org/jsonevil (provided without support or warranty) JSON (JavaScript Object Notation) (org.json:json:20090211 - http://www.json.org/java/index.html) See 36 other apache projects that have done this: https://issues.apache.org/jira/issues/?jql=text%20~%20%22JSON%20EVIL%22 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-369) Release requires optional profile during prepare step
[ https://issues.apache.org/jira/browse/RYA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-369: --- Description: When preparing the release put all the optional profiles during mvn release:prepare step. Update the release instructions. mvn clean release:prepare -P geoindexing -Darguments="-DskipTests" This allows the pom.xml files version update. Also these two have old versions: "3.2.10-incubating-SNAPSHOT" osgi/pom.xml osgi/sesame-runtime-osgi/pom.xml verify with: grep -r SNAPSHOT rya-project-3.2.11-incubating was: When preparing the release put all the optional profiles during mvn release:prepare step. Update the release instructions. mvn clean release:prepare -P geoindexing -Darguments="-DskipTests" This allows the pom.xml files version update. > Release requires optional profile during prepare step > - > > Key: RYA-369 > URL: https://issues.apache.org/jira/browse/RYA-369 > Project: Rya > Issue Type: Task >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Fix For: 3.2.11 > > > When preparing the release put all the optional profiles during mvn > release:prepare step. > Update the release instructions. > mvn clean release:prepare -P geoindexing -Darguments="-DskipTests" > This allows the pom.xml files version update. > Also these two have old versions: "3.2.10-incubating-SNAPSHOT" > osgi/pom.xml > osgi/sesame-runtime-osgi/pom.xml > verify with: > grep -r SNAPSHOT rya-project-3.2.11-incubating -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-369) Release requires optional profile during prepare step
David W. Lotts created RYA-369: -- Summary: Release requires optional profile during prepare step Key: RYA-369 URL: https://issues.apache.org/jira/browse/RYA-369 Project: Rya Issue Type: Task Reporter: David W. Lotts Assignee: David W. Lotts Priority: Blocker Fix For: 3.2.11 When preparing the release put all the optional profiles during mvn release:prepare step. Update the release instructions. mvn clean release:prepare -P geoindexing -Darguments="-DskipTests" This allows the pom.xml files version update. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-368) Create a Rya Shell for MongoDB
[ https://issues.apache.org/jira/browse/RYA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-368: --- Affects Version/s: (was: 3.2.12) > Create a Rya Shell for MongoDB > -- > > Key: RYA-368 > URL: https://issues.apache.org/jira/browse/RYA-368 > Project: Rya > Issue Type: Improvement >Reporter: Ray Morcos >Priority: Minor > Fix For: 3.2.12 > > > The Rya Shell will be created for MongoDB. Command functions will be similar > to the Rya Shell for Acumullo. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-367) Perform 3.2.11-RC2 Release
[ https://issues.apache.org/jira/browse/RYA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-367: --- Description: This is an issue to capture all of the issues that will be resolved in the next RC also includes:RYA-362 it's already a subtask was: This is an issue to capture all of the issues that will be resolved in the next RC also includes:RYA-362 Improve no-arg error message for shell command create-pcj it's already a subtask > Perform 3.2.11-RC2 Release > -- > > Key: RYA-367 > URL: https://issues.apache.org/jira/browse/RYA-367 > Project: Rya > Issue Type: Improvement >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: release > Fix For: 3.2.11 > > > This is an issue to capture all of the issues that will be resolved in the > next RC > also includes:RYA-362 it's already a subtask -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-367) Perform 3.2.11-RC2 Release
[ https://issues.apache.org/jira/browse/RYA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-367: --- Description: This is an issue to capture all of the issues that will be resolved in the next RC also includes:RYA-362 Improve no-arg error message for shell command create-pcj it's already a subtask was:This is an issue to capture all of the issues that will be resolved in the next RC > Perform 3.2.11-RC2 Release > -- > > Key: RYA-367 > URL: https://issues.apache.org/jira/browse/RYA-367 > Project: Rya > Issue Type: Improvement >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: release > Fix For: 3.2.11 > > > This is an issue to capture all of the issues that will be resolved in the > next RC > also includes:RYA-362 Improve no-arg error message for shell command > create-pcj > it's already a subtask -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (RYA-361) JCalendar library has an incompatible license
[ https://issues.apache.org/jira/browse/RYA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts resolved RYA-361. Resolution: Fixed > JCalendar library has an incompatible license > - > > Key: RYA-361 > URL: https://issues.apache.org/jira/browse/RYA-361 > Project: Rya > Issue Type: Sub-task > Components: clients, export >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: export, license > Fix For: 3.2.11 > > > rya.export depends on JCalendar which is LGPL [1] (brought in by RYA-123) > Its usage should be replaced and removed from the pom.xml(s). > This is blocking the release of 3.2.11 > [1]https://toedter.com/jcalendar/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-360) Header issues: Correct Notice file year, fix wrong Apache License, s/RYA/Apache Rya/ in the README
[ https://issues.apache.org/jira/browse/RYA-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-360: --- Issue Type: Sub-task (was: Task) Parent: RYA-367 > Header issues: Correct Notice file year, fix wrong Apache License, > s/RYA/Apache Rya/ in the README > -- > > Key: RYA-360 > URL: https://issues.apache.org/jira/browse/RYA-360 > Project: Rya > Issue Type: Sub-task > Components: docs >Affects Versions: 3.2.10 >Reporter: David W. Lotts >Assignee: Jeff Dasch >Priority: Blocker > Fix For: 3.2.11 > > > These were found as part of preparing for 3.2.11 release. > * Copyright year in NOTICE needs updating > * s/RYA/Apache Rya/ in the README > * This file has the wrong license header (including a copyright line which > should not be present): > extras/rya.export/export.client/src/main/java/org/apache/rya/export/client/conf/TimeUtils.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-361) JCalendar library has an incompatible license
[ https://issues.apache.org/jira/browse/RYA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-361: --- Issue Type: Sub-task (was: Improvement) Parent: RYA-367 > JCalendar library has an incompatible license > - > > Key: RYA-361 > URL: https://issues.apache.org/jira/browse/RYA-361 > Project: Rya > Issue Type: Sub-task > Components: clients, export >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: export, license > Fix For: 3.2.11 > > > rya.export depends on JCalendar which is LGPL [1] (brought in by RYA-123) > Its usage should be replaced and removed from the pom.xml(s). > This is blocking the release of 3.2.11 > [1]https://toedter.com/jcalendar/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-367) Perform 3.2.11-RC2 Release
David W. Lotts created RYA-367: -- Summary: Perform 3.2.11-RC2 Release Key: RYA-367 URL: https://issues.apache.org/jira/browse/RYA-367 Project: Rya Issue Type: Improvement Reporter: David W. Lotts Assignee: David W. Lotts Priority: Blocker Fix For: 3.2.11 This is an issue to capture all of the issues that will be resolved in the next RC -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (RYA-361) JCalendar library has an incompatible license
[ https://issues.apache.org/jira/browse/RYA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reassigned RYA-361: -- Assignee: David W. Lotts (was: Eric White) > JCalendar library has an incompatible license > - > > Key: RYA-361 > URL: https://issues.apache.org/jira/browse/RYA-361 > Project: Rya > Issue Type: Improvement > Components: clients, export >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: export, license > Fix For: 3.2.11 > > > rya.export depends on JCalendar which is LGPL [1] (brought in by RYA-123) > Its usage should be replaced and removed from the pom.xml(s). > This is blocking the release of 3.2.11 > [1]https://toedter.com/jcalendar/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-363) Unit tests fail with no information when mongoDB fails to start
David W. Lotts created RYA-363:
--
Summary: Unit tests fail with no information when mongoDB fails to
start
Key: RYA-363
URL: https://issues.apache.org/jira/browse/RYA-363
Project: Rya
Issue Type: Improvement
Affects Versions: 3.2.11
Reporter: David W. Lotts
Assignee: Andrew Smith
Priority: Minor
Fix For: 3.2.12
When MockMongoFactory fails for whatever reason, the logs do not show an error
unless log4J is configured and INFO is logged. This is not the case for a
standard "mvn clean install" so all you see is this:
> java.lang.NullPointerException: null
> at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:191)
> at org.apache.rya.mongodb.MongoDBRdfConfiguration.setMongoClient(
> MongoDBRdfConfiguration.java:267) ...
Change it so that it always shows an error that contains some indication of the
root cause -- even if it says that mongodb failed to initialize, better would
be to show the mongdb output, like below.
This should be in the \[ERROR\] log, not the \[INFO\]
{code}
2017-08-31 14:24:48,466 INFO [Thread-3] mongodb.MockMongoFactory
(Slf4jLevel.java:log(42)) -
[initandlisten] terminate() called. An exception is active; attempting to
gather more information[mongod output]
[initandlisten] std::exception::what(): Resource temporarily unavailable[mongod
output]
Actual exception type: std::system_error[mongod output]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (RYA-361) JCalendar library has an incompatible license
David W. Lotts created RYA-361: -- Summary: JCalendar library has an incompatible license Key: RYA-361 URL: https://issues.apache.org/jira/browse/RYA-361 Project: Rya Issue Type: Improvement Components: export, clients Reporter: David W. Lotts Assignee: Eric White Priority: Blocker Fix For: 3.2.11 rya.export depends on JCalendar which is LGPL [1] (brought in by RYA-123) Its usage should be replaced and removed from the pom.xml(s). This is blocking the release of 3.2.11 [1]https://toedter.com/jcalendar/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-360) Header issues: Correct Notice file year, fix wrong Apache License, s/RYA/Apache Rya/ in the README
David W. Lotts created RYA-360: -- Summary: Header issues: Correct Notice file year, fix wrong Apache License, s/RYA/Apache Rya/ in the README Key: RYA-360 URL: https://issues.apache.org/jira/browse/RYA-360 Project: Rya Issue Type: Task Components: docs Affects Versions: 3.2.10 Reporter: David W. Lotts Assignee: Jeff Dasch Priority: Blocker Fix For: 3.2.11 These were found as part of preparing for 3.2.11 release. * Copyright year in NOTICE needs updating * s/RYA/Apache Rya/ in the README * This file has the wrong license header (including a copyright line which should not be present): extras/rya.export/export.client/src/main/java/org/apache/rya/export/client/conf/TimeUtils.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-117) Add Graphx support
[ https://issues.apache.org/jira/browse/RYA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-117: --- Fix Version/s: 3.2.11 > Add Graphx support > -- > > Key: RYA-117 > URL: https://issues.apache.org/jira/browse/RYA-117 > Project: Rya > Issue Type: Sub-task > Components: clients >Reporter: Andrew Smith >Assignee: Evan Good > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-154) Decouple Configuration for Using PCJs and Using PCJ updater
[ https://issues.apache.org/jira/browse/RYA-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-154: --- Affects Version/s: (was: 3.2.10) > Decouple Configuration for Using PCJs and Using PCJ updater > --- > > Key: RYA-154 > URL: https://issues.apache.org/jira/browse/RYA-154 > Project: Rya > Issue Type: Bug > Components: clients, dao >Reporter: Caleb Meier >Assignee: Caleb Meier > Fix For: 3.2.10 > > > When a user configures a Rya Client to use Precomputed Joins for querying, it > also adds the PrecomputedJoinIndexer to the list of additional indices. This > should not be the case as the PrecomputedJoinIndexer is used to incrementally > update PCJs as data is ingested, while enabling PCJs is a query client > feature that can be used to boost query performance. Given the different > roles of these two features, their configuration should be decoupled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-154) Decouple Configuration for Using PCJs and Using PCJ updater
[ https://issues.apache.org/jira/browse/RYA-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-154: --- Fix Version/s: 3.2.10 > Decouple Configuration for Using PCJs and Using PCJ updater > --- > > Key: RYA-154 > URL: https://issues.apache.org/jira/browse/RYA-154 > Project: Rya > Issue Type: Bug > Components: clients, dao >Reporter: Caleb Meier >Assignee: Caleb Meier > Fix For: 3.2.10 > > > When a user configures a Rya Client to use Precomputed Joins for querying, it > also adds the PrecomputedJoinIndexer to the list of additional indices. This > should not be the case as the PrecomputedJoinIndexer is used to incrementally > update PCJs as data is ingested, while enabling PCJs is a query client > feature that can be used to boost query performance. Given the different > roles of these two features, their configuration should be decoupled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-185) Add load statements from local file command to Rya Console.
[ https://issues.apache.org/jira/browse/RYA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-185: --- Fix Version/s: 3.2.11 > Add load statements from local file command to Rya Console. > --- > > Key: RYA-185 > URL: https://issues.apache.org/jira/browse/RYA-185 > Project: Rya > Issue Type: Improvement > Components: clients >Reporter: Kevin Chilton >Assignee: Kevin Chilton > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-204) Rya Jena Sesame Adapter
[ https://issues.apache.org/jira/browse/RYA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-204: --- Fix Version/s: 3.2.11 > Rya Jena Sesame Adapter > --- > > Key: RYA-204 > URL: https://issues.apache.org/jira/browse/RYA-204 > Project: Rya > Issue Type: New Feature >Reporter: Eric White >Assignee: Eric White > Fix For: 3.2.11 > > > Add the ability to use the Jena API over a Sesame repository. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-219) Add support for exporting to kafka for the rya trigger service
[ https://issues.apache.org/jira/browse/RYA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-219: --- Fix Version/s: 3.2.11 > Add support for exporting to kafka for the rya trigger service > -- > > Key: RYA-219 > URL: https://issues.apache.org/jira/browse/RYA-219 > Project: Rya > Issue Type: Improvement >Reporter: Andrew Smith >Assignee: David W. Lotts > Fix For: 3.2.11 > > > The rya trigger service needs to support the ability to also export to kafka. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-230) Revive Blueprints/Tinkerpop support for Rya
[ https://issues.apache.org/jira/browse/RYA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-230: --- Affects Version/s: 3.2.10 > Revive Blueprints/Tinkerpop support for Rya > --- > > Key: RYA-230 > URL: https://issues.apache.org/jira/browse/RYA-230 > Project: Rya > Issue Type: New Feature > Components: clients >Affects Versions: 3.2.10 >Reporter: Puja Valiyil >Assignee: Puja Valiyil > Fix For: 3.2.11 > > > Previously Rya users could use the SAIL Graph provided with Blueprints as an > adapter for their graph analytics. Since this is no longer maintained, we > should look at providing tinkerpop/gremlin support specific to Rya. > Since there are fewer contracts with Gremlin/Tinkerpop compared to > Spark/GraphX, we can probably make the adapter dependent on only the core > tables. > Statement Metadata could be used for applying properties to edges, and a > specific triple could be added to specify properties on vertices. We could > also not support properties on vertices, but this seems like a cop out. Some > decisions would have to be made as to how much to initially load versus > dynamically query when a user creates a vertice or edge. We could also look > at what other triplestores do to provide properties on vertices/edges. > Stardog might be good place to start -- they do something with reification. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-232) Create a Mongo profile for deploying the rest service
[ https://issues.apache.org/jira/browse/RYA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-232: --- Fix Version/s: 3.2.11 > Create a Mongo profile for deploying the rest service > - > > Key: RYA-232 > URL: https://issues.apache.org/jira/browse/RYA-232 > Project: Rya > Issue Type: New Feature > Components: clients >Reporter: Puja Valiyil > Fix For: 3.2.11 > > > Currently a user has to manually copy and paste some spring files to deploy > to a mongo based deployment (the default for the rest service deploys > accumulo specific configuration). There should be a profile that includes > the mongo spring files instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-230) Revive Blueprints/Tinkerpop support for Rya
[ https://issues.apache.org/jira/browse/RYA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-230: --- Fix Version/s: 3.2.11 > Revive Blueprints/Tinkerpop support for Rya > --- > > Key: RYA-230 > URL: https://issues.apache.org/jira/browse/RYA-230 > Project: Rya > Issue Type: New Feature > Components: clients >Reporter: Puja Valiyil >Assignee: Puja Valiyil > Fix For: 3.2.11 > > > Previously Rya users could use the SAIL Graph provided with Blueprints as an > adapter for their graph analytics. Since this is no longer maintained, we > should look at providing tinkerpop/gremlin support specific to Rya. > Since there are fewer contracts with Gremlin/Tinkerpop compared to > Spark/GraphX, we can probably make the adapter dependent on only the core > tables. > Statement Metadata could be used for applying properties to edges, and a > specific triple could be added to specify properties on vertices. We could > also not support properties on vertices, but this seems like a cop out. Some > decisions would have to be made as to how much to initially load versus > dynamically query when a user creates a vertice or edge. We could also look > at what other triplestores do to provide properties on vertices/edges. > Stardog might be good place to start -- they do something with reification. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-231) Revive Giraph Support
[ https://issues.apache.org/jira/browse/RYA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-231: --- Affects Version/s: 3.2.10 > Revive Giraph Support > - > > Key: RYA-231 > URL: https://issues.apache.org/jira/browse/RYA-231 > Project: Rya > Issue Type: New Feature > Components: clients >Affects Versions: 3.2.10 >Reporter: Puja Valiyil >Assignee: Puja Valiyil > Fix For: 3.2.11 > > > Giraph support was no longer maintained for Rya some time after the initial > import into Apache. We should look at reviving and updating it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-231) Revive Giraph Support
[ https://issues.apache.org/jira/browse/RYA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-231: --- Fix Version/s: 3.2.11 > Revive Giraph Support > - > > Key: RYA-231 > URL: https://issues.apache.org/jira/browse/RYA-231 > Project: Rya > Issue Type: New Feature > Components: clients >Affects Versions: 3.2.10 >Reporter: Puja Valiyil >Assignee: Puja Valiyil > Fix For: 3.2.11 > > > Giraph support was no longer maintained for Rya some time after the initial > import into Apache. We should look at reviving and updating it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-249) Mongo GeoIndexer assumes polygon when performing within
[ https://issues.apache.org/jira/browse/RYA-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-249: --- Affects Version/s: 3.2.10 > Mongo GeoIndexer assumes polygon when performing within > --- > > Key: RYA-249 > URL: https://issues.apache.org/jira/browse/RYA-249 > Project: Rya > Issue Type: Bug >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > > Mongo Storage strategy assumes a polygon object is being used when performing > a WITHIN operation. If a polygon is not provided the operation breaks on > mongodb instead of in RYA. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-241) Add Geowave support
[ https://issues.apache.org/jira/browse/RYA-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-241: --- Fix Version/s: 3.2.11 > Add Geowave support > --- > > Key: RYA-241 > URL: https://issues.apache.org/jira/browse/RYA-241 > Project: Rya > Issue Type: New Feature >Reporter: Eric White >Assignee: Eric White > Fix For: 3.2.11 > > > Add in Geowave as an alternative to Geomesa -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-249) Mongo GeoIndexer assumes polygon when performing within
[ https://issues.apache.org/jira/browse/RYA-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-249: --- Fix Version/s: 3.2.11 > Mongo GeoIndexer assumes polygon when performing within > --- > > Key: RYA-249 > URL: https://issues.apache.org/jira/browse/RYA-249 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > > Mongo Storage strategy assumes a polygon object is being used when performing > a WITHIN operation. If a polygon is not provided the operation breaks on > mongodb instead of in RYA. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-255) Provide an example class that demonstrates Prospector.
[ https://issues.apache.org/jira/browse/RYA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-255: --- Fix Version/s: 3.2.11 > Provide an example class that demonstrates Prospector. > -- > > Key: RYA-255 > URL: https://issues.apache.org/jira/browse/RYA-255 > Project: Rya > Issue Type: Improvement >Reporter: Kevin Chilton >Assignee: Kevin Chilton > Fix For: 3.2.11 > > > Create an example class that demonstrates how the Prospector may be used to > build and harvest information about a Rya instance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-254) Add a factory method to ProspectorServiceEvalStatsDAO that only takes a Configuration object.
[ https://issues.apache.org/jira/browse/RYA-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-254: --- Fix Version/s: 3.2.11 > Add a factory method to ProspectorServiceEvalStatsDAO that only takes a > Configuration object. > - > > Key: RYA-254 > URL: https://issues.apache.org/jira/browse/RYA-254 > Project: Rya > Issue Type: Improvement >Reporter: Kevin Chilton >Assignee: Kevin Chilton > Fix For: 3.2.11 > > > The team would like a factory method for creating a > ProspectorServiceEvalStatsDAO that only takes a Configuration object to > initialize itself. This is meant to be a convenience method for those who do > not want to reuse a Connector or wrap the Configuration object as the > required RdfCloudTripleStoreConfiguration object. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-257) Add Geo and Temporal filtering and Geo type support to Entity Index
[ https://issues.apache.org/jira/browse/RYA-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-257: --- Fix Version/s: 3.2.11 > Add Geo and Temporal filtering and Geo type support to Entity Index > --- > > Key: RYA-257 > URL: https://issues.apache.org/jira/browse/RYA-257 > Project: Rya > Issue Type: Improvement >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > > This is mainly adding filtering support to the Entity Index -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-262) AccumuloDocIdIndexer throws exception when authorizations are empty string or null.
[ https://issues.apache.org/jira/browse/RYA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-262: --- Fix Version/s: 3.2.11 > AccumuloDocIdIndexer throws exception when authorizations are empty string or > null. > --- > > Key: RYA-262 > URL: https://issues.apache.org/jira/browse/RYA-262 > Project: Rya > Issue Type: Bug >Reporter: Kevin Chilton >Assignee: Kevin Chilton >Priority: Minor > Fix For: 3.2.11 > > > AccumuloDocIndexer.runQuery(StarQuery query, Collection ranges) throws > an exception if the configuration object never set authorizations or if the > authorizations are set to the empty string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-263) Add Type Injection to Entity Indexer
[ https://issues.apache.org/jira/browse/RYA-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-263: --- Fix Version/s: 3.2.11 > Add Type Injection to Entity Indexer > > > Key: RYA-263 > URL: https://issues.apache.org/jira/browse/RYA-263 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > > The Entity Indexer has no way of populating types. > Create a String based configuration field that gets parsed (JSON?) > and added to TypeStorage during init(). > Perform checks, where the DB has priority over conflicting typeIDs, to > prevent duplicate types -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-263) Add Type Injection to Entity Indexer
[ https://issues.apache.org/jira/browse/RYA-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-263: --- Affects Version/s: 3.2.10 > Add Type Injection to Entity Indexer > > > Key: RYA-263 > URL: https://issues.apache.org/jira/browse/RYA-263 > Project: Rya > Issue Type: Bug >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > > The Entity Indexer has no way of populating types. > Create a String based configuration field that gets parsed (JSON?) > and added to TypeStorage during init(). > Perform checks, where the DB has priority over conflicting typeIDs, to > prevent duplicate types -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-268) ConfigUtils replaces 2 config fields when establishing indexers
[ https://issues.apache.org/jira/browse/RYA-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-268: --- Fix Version/s: 3.2.11 > ConfigUtils replaces 2 config fields when establishing indexers > --- > > Key: RYA-268 > URL: https://issues.apache.org/jira/browse/RYA-268 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.11 > > > ConfigUtils replaces 2 fields when setting up indexers. > Additional Indexers > Additional Optimizers > any optimizer or indexer that is in the field, even if in a config file > provided by a user, is replaced. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-316) Long LineStrings break MongoDB ingest
[ https://issues.apache.org/jira/browse/RYA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-316: --- Fix Version/s: 3.2.11 > Long LineStrings break MongoDB ingest > - > > Key: RYA-316 > URL: https://issues.apache.org/jira/browse/RYA-316 > Project: Rya > Issue Type: Bug > Components: dao >Reporter: Aaron Mihalik >Assignee: Andrew Smith > Fix For: 3.2.11 > > > MongoDB will reject statements they contain very long linestrings. > Basically, the mongodb index key is limited to 1024 chars, so the insert will > fail if the literal is longer. > [Here is some example > code|https://github.com/amihalik/rya-mongo-debugging/blob/master/src/main/java/com/github/amihalik/rya/mongo/debugging/linestring/LoadLineString.java]. > I think the inserts will work if you use 10 points, but fail if you use > linestrings with 100 points. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-313) Rya Mongo Blows up on Large result sets
[
https://issues.apache.org/jira/browse/RYA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts updated RYA-313:
---
Fix Version/s: 3.2.11
> Rya Mongo Blows up on Large result sets
> ---
>
> Key: RYA-313
> URL: https://issues.apache.org/jira/browse/RYA-313
> Project: Rya
> Issue Type: Bug
> Components: dao
>Affects Versions: 3.2.10
> Environment: Mongo DB with Rya 3.2.11-SNAPSHOT with a lot of data in
> Rya
>Reporter: Aaron Mihalik
>Assignee: Andrew Smith
> Fix For: 3.2.11
>
>
> Simple queries that return a lot of results fail because mongo is trying to
> send all of the results back at once. For instance, if I have a lot of data
> and run something like:
> {noformat}
> SELECT * WHERE
> {
> ?s a ?t.
> }
> {noformat}
> I will get this exception.
> {noformat}
> Caused by: com.mongodb.MongoCommandException: Command failed with error
> 16389: 'aggregation result exceeds maximum document size (16MB)' on server
> localhost:27017. The full response is { "ok" : 0.0, "errmsg" : "aggregation
> result exceeds maximum document size (16MB)", "code" : 16389 }
> {noformat}
> I think we need to toss in a "AggregationOptions with Batch = 1000", but I
> couldn't get that to work immediately. Somebody with more mongo experience
> needs to look at this.
> [Here is the line of
> code|https://github.com/apache/incubator-rya/blob/master/dao/mongodb.rya/src/main/java/org/apache/rya/mongodb/iter/RyaStatementBindingSetCursorIterator.java#L114]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (RYA-123) Mongo Support in the Merge Tool
[ https://issues.apache.org/jira/browse/RYA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-123: --- Affects Version/s: (was: 3.2.10) > Mongo Support in the Merge Tool > --- > > Key: RYA-123 > URL: https://issues.apache.org/jira/browse/RYA-123 > Project: Rya > Issue Type: New Feature >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.10 > > > Add mongo support to the merge tool to allow cloning: > Accumulo --> Mongo > Mongo --> Accumulo > Accumulo --> Accumulo > Mongo --> Mongo -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-123) Mongo Support in the Merge Tool
[ https://issues.apache.org/jira/browse/RYA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-123: --- Fix Version/s: 3.2.10 > Mongo Support in the Merge Tool > --- > > Key: RYA-123 > URL: https://issues.apache.org/jira/browse/RYA-123 > Project: Rya > Issue Type: New Feature >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.10 > > > Add mongo support to the merge tool to allow cloning: > Accumulo --> Mongo > Mongo --> Accumulo > Accumulo --> Accumulo > Mongo --> Mongo -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-128) Refactor existing tests
[ https://issues.apache.org/jira/browse/RYA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-128: --- Fix Version/s: 3.2.11 > Refactor existing tests > --- > > Key: RYA-128 > URL: https://issues.apache.org/jira/browse/RYA-128 > Project: Rya > Issue Type: Sub-task >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Eric White > Fix For: 3.2.11 > > > Refactor the existing tests to use refactored merge tool -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-127) Cloning/Merging mongo functionality
[ https://issues.apache.org/jira/browse/RYA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-127: --- Fix Version/s: 3.2.10 > Cloning/Merging mongo functionality > --- > > Key: RYA-127 > URL: https://issues.apache.org/jira/browse/RYA-127 > Project: Rya > Issue Type: Sub-task >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.10 > > > Implement Cloning/Merging functionality in Mongo -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-140) Copy Tool - Mongo Support
[ https://issues.apache.org/jira/browse/RYA-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-140: --- Fix Version/s: 3.2.10 > Copy Tool - Mongo Support > - > > Key: RYA-140 > URL: https://issues.apache.org/jira/browse/RYA-140 > Project: Rya > Issue Type: Sub-task > Components: clients >Affects Versions: 3.2.10 >Reporter: Kevin Chilton >Assignee: Eric White > Fix For: 3.2.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-161) Integrate Mongo and Accumulo in a client
[ https://issues.apache.org/jira/browse/RYA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-161: --- Fix Version/s: 3.2.10 > Integrate Mongo and Accumulo in a client > > > Key: RYA-161 > URL: https://issues.apache.org/jira/browse/RYA-161 > Project: Rya > Issue Type: Sub-task >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.10 > > > With Mongo and Accumulo functionality implemented, a client is needed to call > into and use the implementations -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-126) Refactor Accumulo functionality in new interfaces
[ https://issues.apache.org/jira/browse/RYA-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-126: --- Fix Version/s: 3.2.10 > Refactor Accumulo functionality in new interfaces > - > > Key: RYA-126 > URL: https://issues.apache.org/jira/browse/RYA-126 > Project: Rya > Issue Type: Sub-task >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Eric White > Fix For: 3.2.10 > > > Re-implement accumulo functionality with new interfaces. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-141) Copy Tool - Accumulo Support
[ https://issues.apache.org/jira/browse/RYA-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-141: --- Fix Version/s: 3.2.10 > Copy Tool - Accumulo Support > > > Key: RYA-141 > URL: https://issues.apache.org/jira/browse/RYA-141 > Project: Rya > Issue Type: Sub-task > Components: clients >Affects Versions: 3.2.10 >Reporter: Kevin Chilton >Assignee: Eric White > Fix For: 3.2.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-121) Store contextual metadata for individual triples
[ https://issues.apache.org/jira/browse/RYA-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-121: --- Fix Version/s: 3.2.11 > Store contextual metadata for individual triples > > > Key: RYA-121 > URL: https://issues.apache.org/jira/browse/RYA-121 > Project: Rya > Issue Type: New Feature > Components: dao >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Puja Valiyil > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-168) Support for property chains for Rya query inference
[ https://issues.apache.org/jira/browse/RYA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-168: --- Fix Version/s: 3.2.10 > Support for property chains for Rya query inference > --- > > Key: RYA-168 > URL: https://issues.apache.org/jira/browse/RYA-168 > Project: Rya > Issue Type: New Feature > Components: erence >Reporter: Puja Valiyil >Assignee: Puja Valiyil > Fix For: 3.2.10 > > > It would be useful to provide propertyChain support for backwards chaining > inference. This is relatively straight forward and can draw on the other > query expansion paradigms in Rya's exisitng inference. Some research needs > to be done to determine how property chains look when ingested into Rya > (serialized into N-Triples). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-104) Mongo Support in Rya Administrative Shell
[ https://issues.apache.org/jira/browse/RYA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-104: --- Affects Version/s: (was: 3.2.10) 3.2.9 > Mongo Support in Rya Administrative Shell > - > > Key: RYA-104 > URL: https://issues.apache.org/jira/browse/RYA-104 > Project: Rya > Issue Type: New Feature >Affects Versions: 3.2.9 >Reporter: Andrew Smith >Assignee: Kevin Chilton > Fix For: 3.2.10 > > > Implement mongo support for the admin shell. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-104) Mongo Support in Rya Administrative Shell
[ https://issues.apache.org/jira/browse/RYA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-104: --- Fix Version/s: 3.2.10 > Mongo Support in Rya Administrative Shell > - > > Key: RYA-104 > URL: https://issues.apache.org/jira/browse/RYA-104 > Project: Rya > Issue Type: New Feature >Affects Versions: 3.2.9 >Reporter: Andrew Smith >Assignee: Kevin Chilton > Fix For: 3.2.10 > > > Implement mongo support for the admin shell. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-133) Mongo Secondary indexers are broken
[ https://issues.apache.org/jira/browse/RYA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-133: --- Fix Version/s: 3.2.10 > Mongo Secondary indexers are broken > --- > > Key: RYA-133 > URL: https://issues.apache.org/jira/browse/RYA-133 > Project: Rya > Issue Type: Sub-task >Reporter: Andrew Smith >Assignee: Andrew Smith > Fix For: 3.2.10 > > > With the creation of integration tests for mongo support in the rya admin > shell, it was discovered that the refactoring of the mongo secondary indexers > broke some of the functionality. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-75) Add Merge Tool to Rya
[ https://issues.apache.org/jira/browse/RYA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-75: -- Fix Version/s: 3.2.10 > Add Merge Tool to Rya > - > > Key: RYA-75 > URL: https://issues.apache.org/jira/browse/RYA-75 > Project: Rya > Issue Type: New Feature >Reporter: Eric White > Fix For: 3.2.10 > > > The Merge Tool feature merges a child's Accumulo instance to its parent > instance after the child has collected/modified its data set. The Copy Tool > allows the creation of a child instance from a parent Accumulo instance and > the data that is copied can be filtered by time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-75) Add Merge Tool to Rya
[ https://issues.apache.org/jira/browse/RYA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-75: -- Affects Version/s: (was: 3.2.10) > Add Merge Tool to Rya > - > > Key: RYA-75 > URL: https://issues.apache.org/jira/browse/RYA-75 > Project: Rya > Issue Type: New Feature >Reporter: Eric White > Fix For: 3.2.10 > > > The Merge Tool feature merges a child's Accumulo instance to its parent > instance after the child has collected/modified its data set. The Copy Tool > allows the creation of a child instance from a parent Accumulo instance and > the data that is copied can be filtered by time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-165) Fluo PCJ maintenance should use ColumnVisibility.flatten() to simplify the visibility expression
[
https://issues.apache.org/jira/browse/RYA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts updated RYA-165:
---
Affects Version/s: 3.2.9
> Fluo PCJ maintenance should use ColumnVisibility.flatten() to simplify the
> visibility expression
>
>
> Key: RYA-165
> URL: https://issues.apache.org/jira/browse/RYA-165
> Project: Rya
> Issue Type: Bug
> Components: dao
>Affects Versions: 3.2.9
>Reporter: Puja Valiyil
>Assignee: Kevin Chilton
>Priority: Critical
> Fix For: 3.2.10
>
>
> The Fluo application that maintains PCJ indices currently creates complex
> visibility expressions that grow with every join that is part of the SPARQL
> query.
> For example, if you create a PCJ for the following SPARQL:
> {code}
> SELECT ?customer ?worker ?city {
> ?customer ?worker.
> ?worker ?city.
> ?worker .
> }
> {code}
> And you insert the following Statements:
> {code}
> Statement: " " Visibility: "u"
> Statement: " " Visibility: "u"
> Statement: " " Visibility: "u"
> {code}
> Then the following result will be exported to the PCJ index:
> {code}
> BindingSet: {{"customer", "urn:Alice"}, {"worker","urn:Bob"}, {"city",
> "urn:Happyville"} Visibility: "(u&u)&u"
> {code}
> That visibility expression could also be represented as just "u".
> ColumnVisibility.flatten() calls may be used to iteratively simplify the
> logical expression, so update the Fluo application to do so before exporting
> the result.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (RYA-165) Fluo PCJ maintenance should use ColumnVisibility.flatten() to simplify the visibility expression
[
https://issues.apache.org/jira/browse/RYA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts updated RYA-165:
---
Fix Version/s: 3.2.10
> Fluo PCJ maintenance should use ColumnVisibility.flatten() to simplify the
> visibility expression
>
>
> Key: RYA-165
> URL: https://issues.apache.org/jira/browse/RYA-165
> Project: Rya
> Issue Type: Bug
> Components: dao
>Reporter: Puja Valiyil
>Assignee: Kevin Chilton
>Priority: Critical
> Fix For: 3.2.10
>
>
> The Fluo application that maintains PCJ indices currently creates complex
> visibility expressions that grow with every join that is part of the SPARQL
> query.
> For example, if you create a PCJ for the following SPARQL:
> {code}
> SELECT ?customer ?worker ?city {
> ?customer ?worker.
> ?worker ?city.
> ?worker .
> }
> {code}
> And you insert the following Statements:
> {code}
> Statement: " " Visibility: "u"
> Statement: " " Visibility: "u"
> Statement: " " Visibility: "u"
> {code}
> Then the following result will be exported to the PCJ index:
> {code}
> BindingSet: {{"customer", "urn:Alice"}, {"worker","urn:Bob"}, {"city",
> "urn:Happyville"} Visibility: "(u&u)&u"
> {code}
> That visibility expression could also be represented as just "u".
> ColumnVisibility.flatten() calls may be used to iteratively simplify the
> logical expression, so update the Fluo application to do so before exporting
> the result.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (RYA-109) Add Spark support
[ https://issues.apache.org/jira/browse/RYA-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-109: --- Affects Version/s: (was: 3.2.10) 3.2.11 > Add Spark support > - > > Key: RYA-109 > URL: https://issues.apache.org/jira/browse/RYA-109 > Project: Rya > Issue Type: New Feature > Components: clients >Affects Versions: 3.2.11 >Reporter: Andrew Smith >Assignee: Evan Good > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-109) Add Spark support
[ https://issues.apache.org/jira/browse/RYA-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-109: --- Fix Version/s: 3.2.11 > Add Spark support > - > > Key: RYA-109 > URL: https://issues.apache.org/jira/browse/RYA-109 > Project: Rya > Issue Type: New Feature > Components: clients >Affects Versions: 3.2.11 >Reporter: Andrew Smith >Assignee: Evan Good > Fix For: 3.2.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-151) Rya Test Bed
[ https://issues.apache.org/jira/browse/RYA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-151: --- Fix Version/s: 3.2.10 > Rya Test Bed > > > Key: RYA-151 > URL: https://issues.apache.org/jira/browse/RYA-151 > Project: Rya > Issue Type: Wish > Components: clients, dao >Reporter: Puja Valiyil >Assignee: Kevin Chilton > Fix For: 3.2.10 > > > It would be nice if there was a test bed checked in with Rya that could be > used for benchmark testing. This test bed should include options for > uploading data to a rya instance, then issuing some benchmark queries (and > timing them in a way that everyone agrees is sound). It could be a command > line tool. It should be dao agnostic (work on either mongo, accumulo, etc.). > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-144) New Secondary Index: Smart URI
[ https://issues.apache.org/jira/browse/RYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-144: --- Fix Version/s: 3.2.11 > New Secondary Index: Smart URI > -- > > Key: RYA-144 > URL: https://issues.apache.org/jira/browse/RYA-144 > Project: Rya > Issue Type: New Feature >Reporter: Kevin Chilton >Assignee: Andrew Smith > Fix For: 3.2.11 > > > This is intended primarily for the Mongo implementation of Rya. > A purpose of this is so that we can discover it though the SPARQL query > interface. > Suppose you have a star entity named 'David': > David is a person > david has an SSN > david has a birthday, > So a URI holding all of this information about David could look like this: > HTTP://Person&name=david&SSN=111-11-&birthday=20160101 > This makes it so that instead of using 3 joins it is only a scan. > -- > Current open pull request does not have SPARQL support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-106) Rya Security - Maintain users who are allowed to access the Rya Instance automatically.
[ https://issues.apache.org/jira/browse/RYA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-106: --- Fix Version/s: 3.2.11 > Rya Security - Maintain users who are allowed to access the Rya Instance > automatically. > --- > > Key: RYA-106 > URL: https://issues.apache.org/jira/browse/RYA-106 > Project: Rya > Issue Type: New Feature >Reporter: Kevin Chilton >Assignee: Kevin Chilton > Fix For: 3.2.11 > > > If the root Accumulo user creates a new PCJ table, other users are not able > to read from it until they are explicitly given permission to outside of Rya. > Creating new PCJs should automatically grant access to users who are allowed > to use that instance of Rya. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-83) select * where { s? p? o? } query crashed
[
https://issues.apache.org/jira/browse/RYA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts updated RYA-83:
--
Fix Version/s: 3.2.11
> select * where { s? p? o? } query crashed
> -
>
> Key: RYA-83
> URL: https://issues.apache.org/jira/browse/RYA-83
> Project: Rya
> Issue Type: Bug
> Environment: Accumulo 1.6.5 installed on EMR 4.6.0 (Hadoop 2.6.0)
>Reporter: Kiet Ly
>Assignee: David W. Lotts
> Fix For: 3.2.11
>
>
> I ran this query using REST
> http://10.162.96.61:8000/web.rya/queryrdf?query=select * where { ?s ?p ?o }
> and it crashed. I just want to see the triples that I had inserted. I ran the
> query against the RYA I built from develop branch with accumulo 1.6.5.
> The error indicate this query is not supported, "select * where { ?s ?p ?o
> }".
> {code}
> java.lang.IllegalArgumentException: TriplePattern[RyaStatement{subject=null,
> predicate=null, object=null, context=null, qualifier=null,
> columnVisibility=null, value=null, timestamp=1465307441120}] not supported
>
> mvm.rya.accumulo.query.AccumuloRyaQueryEngine.queryWithBindingSet(AccumuloRyaQueryEngine.java:142)
>
> mvm.rya.accumulo.query.AccumuloRyaQueryEngine.queryWithBindingSet(AccumuloRyaQueryEngine.java:81)
> mvm.rya.api.persist.utils.RyaDAOHelper.query(RyaDAOHelper.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (RYA-272) Create Geo examples in Geo Project
[ https://issues.apache.org/jira/browse/RYA-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-272. -- Resolution: Fixed Assignee: David W. Lotts (was: Puja Valiyil ) Fix Version/s: 3.2.11 > Create Geo examples in Geo Project > -- > > Key: RYA-272 > URL: https://issues.apache.org/jira/browse/RYA-272 > Project: Rya > Issue Type: Task > Components: examples >Affects Versions: 3.2.10 >Reporter: Caleb Meier >Assignee: David W. Lotts > Fix For: 3.2.11 > > > There are a number of old geo examples in the examples in the Indexing > Example project that are commented out. These need to be removed and used to > form an example class for the geo project. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (RYA-324) geoWave and geoMesa depend on different versions of the GeoTools
[ https://issues.apache.org/jira/browse/RYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-324. -- Resolution: Fixed > geoWave and geoMesa depend on different versions of the GeoTools > > > Key: RYA-324 > URL: https://issues.apache.org/jira/browse/RYA-324 > Project: Rya > Issue Type: Bug > Components: sail >Affects Versions: 3.2.10 >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: dependencies, geo, refactor > Fix For: 3.2.11 > > > Refactored geo libraries into separate projects/modules/jars. > Geo libraries are optional and turned off by default because the GeoTools is > has an incompatible license. > Further, geoWave and geoMesa depend on different versions of the GeoTools, so > they must be in separate projects. > The new modules (projects) are > geo.common > geo.mongo > geo.geomesa > geo.geowave > These are modules of the project rya.geoindexing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-324) geoWave and geoMesa depend on different versions of the GeoTools
[ https://issues.apache.org/jira/browse/RYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-324: --- Affects Version/s: (was: 3.2.10) 3.2.11 > geoWave and geoMesa depend on different versions of the GeoTools > > > Key: RYA-324 > URL: https://issues.apache.org/jira/browse/RYA-324 > Project: Rya > Issue Type: Bug > Components: sail >Affects Versions: 3.2.10 >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: dependencies, geo, refactor > Fix For: 3.2.11 > > > Refactored geo libraries into separate projects/modules/jars. > Geo libraries are optional and turned off by default because the GeoTools is > has an incompatible license. > Further, geoWave and geoMesa depend on different versions of the GeoTools, so > they must be in separate projects. > The new modules (projects) are > geo.common > geo.mongo > geo.geomesa > geo.geowave > These are modules of the project rya.geoindexing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-324) geoWave and geoMesa depend on different versions of the GeoTools
[ https://issues.apache.org/jira/browse/RYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-324: --- Affects Version/s: (was: 3.2.11) 3.2.10 > geoWave and geoMesa depend on different versions of the GeoTools > > > Key: RYA-324 > URL: https://issues.apache.org/jira/browse/RYA-324 > Project: Rya > Issue Type: Bug > Components: sail >Affects Versions: 3.2.10 >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: dependencies, geo, refactor > Fix For: 3.2.11 > > > Refactored geo libraries into separate projects/modules/jars. > Geo libraries are optional and turned off by default because the GeoTools is > has an incompatible license. > Further, geoWave and geoMesa depend on different versions of the GeoTools, so > they must be in separate projects. > The new modules (projects) are > geo.common > geo.mongo > geo.geomesa > geo.geowave > These are modules of the project rya.geoindexing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RYA-324) geoWave and geoMesa depend on different versions of the GeoTools
[ https://issues.apache.org/jira/browse/RYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts updated RYA-324: --- Fix Version/s: (was: 3.2.10) 3.2.11 > geoWave and geoMesa depend on different versions of the GeoTools > > > Key: RYA-324 > URL: https://issues.apache.org/jira/browse/RYA-324 > Project: Rya > Issue Type: Bug > Components: sail >Affects Versions: 3.2.10 >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: dependencies, geo, refactor > Fix For: 3.2.11 > > > Refactored geo libraries into separate projects/modules/jars. > Geo libraries are optional and turned off by default because the GeoTools is > has an incompatible license. > Further, geoWave and geoMesa depend on different versions of the GeoTools, so > they must be in separate projects. > The new modules (projects) are > geo.common > geo.mongo > geo.geomesa > geo.geowave > These are modules of the project rya.geoindexing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (RYA-94) Remove from secondary indexes when deleting from DAO
[ https://issues.apache.org/jira/browse/RYA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts closed RYA-94. - Resolution: Fixed Fix Version/s: 3.2.11 fixed as part of another issue. > Remove from secondary indexes when deleting from DAO > > > Key: RYA-94 > URL: https://issues.apache.org/jira/browse/RYA-94 > Project: Rya > Issue Type: Bug >Reporter: Andrew Smith >Assignee: David W. Lotts >Priority: Blocker > Fix For: 3.2.11 > > > Currently, if a delete is made from the DAO, the secondary indexers are not > explicitly notified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RYA-324) geoWave and geoMesa depend on different versions of the GeoTools
David W. Lotts created RYA-324: -- Summary: geoWave and geoMesa depend on different versions of the GeoTools Key: RYA-324 URL: https://issues.apache.org/jira/browse/RYA-324 Project: Rya Issue Type: Bug Components: sail Affects Versions: 3.2.10 Reporter: David W. Lotts Assignee: David W. Lotts Fix For: 3.2.10 Refactored geo libraries into separate projects/modules/jars. Geo libraries are optional and turned off by default because the GeoTools is has an incompatible license. Further, geoWave and geoMesa depend on different versions of the GeoTools, so they must be in separate projects. The new modules (projects) are geo.common geo.mongo geo.geomesa geo.geowave These are modules of the project rya.geoindexing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RYA-266) Temporal index fails to write when using non-mock accumulo
[ https://issues.apache.org/jira/browse/RYA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960939#comment-15960939 ] David W. Lotts commented on RYA-266: Jenkins found a failed test, table name is null: RyaDirectExampleTest(ExamplesTest) Time elapsed: 1.323 sec <<< ERROR! org.openrdf.query.QueryEvaluationException: While creating a scanner for a temporal query. table name=null The temporal index table should have been created by this constructor, if found missing. at org.apache.accumulo.core.client.mock.MockConnector.createScanner(MockConnector.java:111) at org.apache.rya.indexing.accumulo.ConfigUtils.createScanner(ConfigUtils.java:234) ... at org.openrdf.repository.sail.SailTupleQuery.evaluate(SailTupleQuery.java:76) at RyaDirectExample.testAddAndTemporalSearchWithPCJ(RyaDirectExample.java:295) at RyaDirectExample.main(RyaDirectExample.java:106) at ExamplesTest.RyaDirectExampleTest(ExamplesTest.java:35) > Temporal index fails to write when using non-mock accumulo > -- > > Key: RYA-266 > URL: https://issues.apache.org/jira/browse/RYA-266 > Project: Rya > Issue Type: Sub-task > Components: dao, sail > Environment: indexing >Reporter: David W. Lotts >Assignee: David W. Lotts >Priority: Blocker > Labels: flush, index, temporal > Original Estimate: 24h > Remaining Estimate: 24h > > Temporal indexing writes nothing to it's table name: [prefix]temporal. > It does seem to work for a mock instance. It might also work for a large > ingest since it would force a flush. > See the parent RYA-72 for an explanation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RYA-269) Test AccumuloLoadStatementsFileIT fails: depends on old identifier: "urn:mvm.rya/2012/05#version"
David W. Lotts created RYA-269:
--
Summary: Test AccumuloLoadStatementsFileIT fails: depends on old
identifier: "urn:mvm.rya/2012/05#version"
Key: RYA-269
URL: https://issues.apache.org/jira/browse/RYA-269
Project: Rya
Issue Type: Test
Components: build
Environment: API integration test
Reporter: David W. Lotts
Priority: Minor
Integration test class:
org.apache.rya.api.client.accumulo.AccumuloLoadStatementsFileIT
in line 119:
"urn:mvm.rya/2012/05#version"
Should be changed to the new identifier:
"urn:org.apache.rya/2012/05#version"
Test the fix in Eclipse, or, in Maven like this:
{{mvn surefire:test
-Dtest=org.apache.rya.api.client.accumulo.AccumuloLoadStatementsFileIT}}
Find any other references to *mvn* and fix them, or report them if it is not
obvious what to do.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RYA-267) Free text indexing fails to flush writes for non-mock.
David W. Lotts created RYA-267: -- Summary: Free text indexing fails to flush writes for non-mock. Key: RYA-267 URL: https://issues.apache.org/jira/browse/RYA-267 Project: Rya Issue Type: Sub-task Components: dao, sail Reporter: David W. Lotts This is not confirmed, but it works exactly the way temporal indexing work(ed) and so will probably fail the same way. Free text indexing probably writes nothing to it's tables. It probably does work for a mock instance. It might also work for a large ingest since it would force a flush. See the parent RYA-72 for an explanation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RYA-266) Temporal index fails to write when using non-mock accumulo
David W. Lotts created RYA-266: -- Summary: Temporal index fails to write when using non-mock accumulo Key: RYA-266 URL: https://issues.apache.org/jira/browse/RYA-266 Project: Rya Issue Type: Sub-task Components: dao, sail Environment: indexing Reporter: David W. Lotts Assignee: David W. Lotts Priority: Blocker Temporal indexing writes nothing to it's table name: [prefix]temporal. It does seem to work for a mock instance. It might also work for a large ingest since it would force a flush. See the parent RYA-72 for an explanation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RYA-72) AccumuloRyaDAO doesn't flush/close secondary indexers' writers
[ https://issues.apache.org/jira/browse/RYA-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947785#comment-15947785 ] David W. Lotts commented on RYA-72: --- Just had to troubleshoot this. This is also an issue for AccumuloFreeTextIndexer.java. I wrote a patch that implements setMultiTableBatchWriter() and uses the DAO's writer. > AccumuloRyaDAO doesn't flush/close secondary indexers' writers > -- > > Key: RYA-72 > URL: https://issues.apache.org/jira/browse/RYA-72 > Project: Rya > Issue Type: Bug > Components: dao >Reporter: Jesse Hatfield >Assignee: Puja Valiyil > > (Seen with respect to AccumuloTemporalIndexer, unconfirmed which others > exhibit the same problem.) > Secondary indexers use MultiTableBatchWriter to write to Accumulo. This needs > to be flushed in order to actually write data, and should probably be closed > when finished. If this isn't done explicitly, the writer only closes itself > if/when its finalize() method is called. > When interacting with the indexers directly, this is fine: the flush and > close methods on the indexers can be used to call the corresponding methods > on their writers. > But the AccumuloRyaDAO doesn't call these methods (or expose its indexers), > so if an application is interacting with the indexers through the DAO, > there's no way to make sure changes are flushed. The DAO does have its own > MultiTableBatchWriter, however (for writing to the spo/osp/pos tables), and > this writer is flushed and closed properly by the DAO's corresponding methods. > Possible fixes include: > A. Have the DAO flush/close its indexers whenever it does the same with its > own writer. > B. Configure the indexers to use the same writer as the DAO. (The DAO invokes > setMultiTableBatchWriter, but this is an empty method in > AbstractAccumuloIndexer and only the Entity index appears to implement it.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RYA-265) Confusion: geospatial indexing, need to use GeoRyaSailFactory NOT RyaSailFactory
David W. Lotts created RYA-265: -- Summary: Confusion: geospatial indexing, need to use GeoRyaSailFactory NOT RyaSailFactory Key: RYA-265 URL: https://issues.apache.org/jira/browse/RYA-265 Project: Rya Issue Type: Bug Components: sail Environment: Configuration Reporter: David W. Lotts A user reported that his Rya installation was not creating geoindexing index files. They had turned on the Maven profile "-P geoindexing", and enabled sc.use_geo in the configuration but nothing worked. Activate geofunctions by doing the following: maven profile enabled: "mvn ... -P geoindexing" Configure enable: conf.set(ConfigUtils.USE_GEO, "true"); OR --- config.xml ... sc.use_geo true ... --- The cause: using RyaSailFactory. The Fix: Replace: RyaSailFactory With:GeoRyaSailFactory - Perhaps we can check for the Geo index config option being TRUE but the non-geo factory is used and throw an Error or Warning. - Maybe the documentation needs improvement. - Place a comment where Geo indexing is turned on. In the pom.xml and possibly in the configuration examples. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RYA-70) web.rya doesn't deploy indexers correctly
[ https://issues.apache.org/jira/browse/RYA-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David W. Lotts reassigned RYA-70: - Assignee: (was: David W. Lotts) > web.rya doesn't deploy indexers correctly > - > > Key: RYA-70 > URL: https://issues.apache.org/jira/browse/RYA-70 > Project: Rya > Issue Type: Bug > Components: clients >Affects Versions: 3.2.9 >Reporter: Aaron Mihalik >Priority: Critical > > spring-root-extensions.xml configuration doesn’t deploy. it still refers to > old classes (eg. mvm.rya.indexing.accumulo.RyaIndexingSail). Instead, It > looks like you should be using the static method > [“RyaSailFactory.getInstance(conf)”|https://github.com/apache/incubator-rya/blob/develop/extras/indexingExample/src/main/java/RyaDirectExample.java#L92] > to create the sail -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RYA-242) Geo function support in Fluo PCJ sparql queries
[ https://issues.apache.org/jira/browse/RYA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854406#comment-15854406 ] David W. Lotts commented on RYA-242: RDF2J has the functions we need, but we are not on the version that contains those. > Geo function support in Fluo PCJ sparql queries > --- > > Key: RYA-242 > URL: https://issues.apache.org/jira/browse/RYA-242 > Project: Rya > Issue Type: New Feature > Environment: Fluo PCJ >Reporter: David W. Lotts >Assignee: David W. Lotts > Labels: CEP, PCJ, geo > > Rya's Fluo pre-computed joins (PCJ) framework along with Kafka sub/pub > gives makes Rya a strong Complex Event Processor (CEP) -- taking streaming > input statements and generating results to subscribed (kafka topics) queries > (PCJ's). > We have identified geo functions as a major enabler for CEP users. > Currently PCJ can handle basic SPARQL filter functions, but not geo functions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RYA-43) NumberFormatException for large integers
[
https://issues.apache.org/jira/browse/RYA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854404#comment-15854404
]
David W. Lotts commented on RYA-43:
---
Here is a reasonable (great?) SOLUTION!
Making it backward compatible is why this has not been fixed yet. This
solution accomplishes backward compatible by mixing the encoding from
LexiTypeEncoders.bigIntegerEncoder() with the existing
LexiTypeEncoders.integerEncoder().
Here is an idea to make this work backwardly compatible. It should not break
existing Rya repositories:
Encode the java sized integers as-is, then for anything out of range, use
MAX/MIN Integer and concatenate the new big integer encoding.
Pros: Regular integers are unencumbered.
Cons:
The only disadvantage I see is that every large integer literal stored will
have an extra 8 bytes.
Here is the current way of encoding returning a string in class :
org.apache.rya.api.resolver.impl.IntegerRyaTypeResolver
return INTEGER_STRING_TYPE_ENCODER.encode(Integer.parseInt(data));
Here is my replacement:
if (value >= Integer.MAX) { // value is a string, fix this with parseint()
and catch or similar
return INTEGER_STRING_TYPE_ENCODER.encode(Integer.MAX) +
LexiTypeEncoders.bigIntegerEncoder(value) ;
} else if (value <= Integer.MIN) { // fix this also as above.
return INTEGER_STRING_TYPE_ENCODER.encode(Integer.MIN) +
LexiTypeEncoders.bigIntegerEncoder(value) ;
} else {
return INTEGER_STRING_TYPE_ENCODER.encode(Integer.parseInt(data));
}
That's it!
You need to figure out a good way to do the comparison before converting from a
String. Probably using the exception catch makes sense. Also deserialize
needs to be coded in reverse.
david.
> NumberFormatException for large integers
>
>
> Key: RYA-43
> URL: https://issues.apache.org/jira/browse/RYA-43
> Project: Rya
> Issue Type: Bug
>Affects Versions: 3.2.10
>Reporter: Jesse Hatfield
>Assignee: David W. Lotts
> Attachments: integer
>
>
> Attempting to insert a value with datatype {{xsd:integer}} and value outside
> the range of a Java int will fail with an exception.
> It looks like Rya resolves any {{xsd:integer}} as an int, whereas the
> [XMLSchema specification|https://www.w3.org/TR/xmlschema11-2/#integer]
> defines {{xsd:integer}} as the infinite set of all integers (with subsets
> {{xsd:long}} and {{xsd:int}} having bounded range). Therefore we fail to
> parse what should be a valid triple.
> Example input:
> {code}
>
> "9223372036854775807"^^ .{code}
> Result:
> {code}
> $ hadoop jar accumulo.rya-3.2.10-SNAPSHOT-shaded.jar
> mvm.rya.accumulo.mr.fileinput.RdfFileInputTool -conf conf.xml
> -Drdf.tablePrefix=int_bug_ -Drdf.format=N-Triples /input/integer.nt
> [...]
> Error: java.io.IOException:
> mvm.rya.api.resolver.triple.TripleRowResolverException:
> mvm.rya.api.resolver.RyaTypeResolverException: Exception occurred serializing
> data[9223372036854775807]
> at
> mvm.rya.accumulo.RyaTableMutationsFactory.serialize(RyaTableMutationsFactory.java:75)
> at
> mvm.rya.accumulo.mr.fileinput.RdfFileInputTool$StatementToMutationMapper.map(RdfFileInputTool.java:157)
> at
> mvm.rya.accumulo.mr.fileinput.RdfFileInputTool$StatementToMutationMapper.map(RdfFileInputTool.java:124)
> at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: mvm.rya.api.resolver.triple.TripleRowResolverException:
> mvm.rya.api.resolver.RyaTypeResolverException: Exception occurred serializing
> data[9223372036854775807]
> at
> mvm.rya.api.resolver.triple.impl.WholeRowTripleResolver.serialize(WholeRowTripleResolver.java:82)
> at
> mvm.rya.api.resolver.RyaTripleContext.serializeTriple(RyaTripleContext.java:85)
> at
> mvm.rya.accumulo.RyaTableMutationsFactory.serialize(RyaTableMutationsFactory.java:67)
> ... 10 more
> Caused by: mvm.rya.api.resolver.RyaTypeResolverException: Exception occurred
> serializing data[9223372036854775807]
> at
> mvm.rya.api.resolver.impl.IntegerRyaTypeResolver.serializeData(IntegerRyaTypeResolver.java:50)
> at
> mvm.rya.api.resolver.impl.RyaTypeResolverImpl.
[jira] [Assigned] (RYA-43) NumberFormatException for large integers
[
https://issues.apache.org/jira/browse/RYA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts reassigned RYA-43:
-
Assignee: (was: David W. Lotts)
> NumberFormatException for large integers
>
>
> Key: RYA-43
> URL: https://issues.apache.org/jira/browse/RYA-43
> Project: Rya
> Issue Type: Bug
>Affects Versions: 3.2.10
>Reporter: Jesse Hatfield
> Attachments: integer
>
>
> Attempting to insert a value with datatype {{xsd:integer}} and value outside
> the range of a Java int will fail with an exception.
> It looks like Rya resolves any {{xsd:integer}} as an int, whereas the
> [XMLSchema specification|https://www.w3.org/TR/xmlschema11-2/#integer]
> defines {{xsd:integer}} as the infinite set of all integers (with subsets
> {{xsd:long}} and {{xsd:int}} having bounded range). Therefore we fail to
> parse what should be a valid triple.
> Example input:
> {code}
>
> "9223372036854775807"^^ .{code}
> Result:
> {code}
> $ hadoop jar accumulo.rya-3.2.10-SNAPSHOT-shaded.jar
> mvm.rya.accumulo.mr.fileinput.RdfFileInputTool -conf conf.xml
> -Drdf.tablePrefix=int_bug_ -Drdf.format=N-Triples /input/integer.nt
> [...]
> Error: java.io.IOException:
> mvm.rya.api.resolver.triple.TripleRowResolverException:
> mvm.rya.api.resolver.RyaTypeResolverException: Exception occurred serializing
> data[9223372036854775807]
> at
> mvm.rya.accumulo.RyaTableMutationsFactory.serialize(RyaTableMutationsFactory.java:75)
> at
> mvm.rya.accumulo.mr.fileinput.RdfFileInputTool$StatementToMutationMapper.map(RdfFileInputTool.java:157)
> at
> mvm.rya.accumulo.mr.fileinput.RdfFileInputTool$StatementToMutationMapper.map(RdfFileInputTool.java:124)
> at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: mvm.rya.api.resolver.triple.TripleRowResolverException:
> mvm.rya.api.resolver.RyaTypeResolverException: Exception occurred serializing
> data[9223372036854775807]
> at
> mvm.rya.api.resolver.triple.impl.WholeRowTripleResolver.serialize(WholeRowTripleResolver.java:82)
> at
> mvm.rya.api.resolver.RyaTripleContext.serializeTriple(RyaTripleContext.java:85)
> at
> mvm.rya.accumulo.RyaTableMutationsFactory.serialize(RyaTableMutationsFactory.java:67)
> ... 10 more
> Caused by: mvm.rya.api.resolver.RyaTypeResolverException: Exception occurred
> serializing data[9223372036854775807]
> at
> mvm.rya.api.resolver.impl.IntegerRyaTypeResolver.serializeData(IntegerRyaTypeResolver.java:50)
> at
> mvm.rya.api.resolver.impl.RyaTypeResolverImpl.serializeType(RyaTypeResolverImpl.java:82)
> at mvm.rya.api.resolver.RyaContext.serializeType(RyaContext.java:121)
> at
> mvm.rya.api.resolver.triple.impl.WholeRowTripleResolver.serialize(WholeRowTripleResolver.java:64)
> ... 12 more
> Caused by: java.lang.NumberFormatException: For input string:
> "9223372036854775807"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.parseInt(Integer.java:615)
> at
> mvm.rya.api.resolver.impl.IntegerRyaTypeResolver.serializeData(IntegerRyaTypeResolver.java:48)
> ... 15 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RYA-246) Separate Fluo query result exporters, Rya PCJ intermingled kafka triggers
[
https://issues.apache.org/jira/browse/RYA-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts updated RYA-246:
---
Description:
Currently the Fluo query observer framework (FQF) has a great plugin-in-ish way
of doing exports. (See field: {{exporters}} in class:
{{org.apache.rya.indexing.pcj.fluo.app.observers.QueryResultObserver}} )
Exports are query results and the action taken when they occur. Currently
there are two. Despite this awesome framework, there are three interminglings
that can become issues in a production system. Feel free to make sub tasks for
each of these three tasks:
1. Create PCJ independently of alerts/triggers
At query register time (with FQF), optionally create PCJ's and optionally
create alerts (with Alerting) preferably atomically, so if it fails in the
middle it does not leave dangling references and garbage -- currently there is
one method that does everything: CreatePCJ.withRyaInteraction()
2. Enable exporters per query -- currently all queries will be exported on all
globally enabled exporters. When the query is registered (with FQF) specify
the exporters that should be used.
3. Separate export observer queues per exporter -- Currently retrying a failed
export observer will re-export all export types, even if some already
succeeded, causing duplicate triggers.
Also there is a need to refine the terms for java identifiers (for example:
fields, classes) and documentation. Please document here a decision about what
we name different things. The term PCJ are the index tables used by Rya to
optimize it's queries. But sometimes it is used to describe the whole Fluo
framework. Please define a unique term for the following. The starred term
will be used here, but feel free to rename them:
- Rya query optimization PCJ (ex: the Blabla exporter) PCJ*
- Kafka trigger alert notifier (ex: the Foofoo exporter) Alerting*
- Fluo query observer framework (ex: results from the Barbar) FQF*
Unique identifers:
- FQF uses QueryID
- Alerting uses TopicID
- PCJ uses PcjId
Note that currently TopicID is assigned the same as QueryID, but that badly
presupposes queryID's cannot be grouped onto one Topic.
was:
Currently the Fluo query observer framework (FQF) has a great plugin-in-ish way
of doing exports. (See field: {{exporters}} in class:
{{org.apache.rya.indexing.pcj.fluo.app.observers.QueryResultObserver}} )
Exports are query results and the action taken when they occur. Currently
there are two. Despite this awsome framework, there are three interminglings
that can become issues in a production system:
1. Create PCJ independently of alerts/triggers
At query register time (with FQF), optionally create PCJ's and optionally
create alerts (with Alerting) preferably atomically, so if it fails in the
middle it does not leave dangling references and garbage -- currently there is
one method that does everything: CreatePCJ.withRyaInteraction()
2. Enable exporters per query -- currently all queries will be exported on all
globally enabled exporters
3. Separate export observer queues per exporter -- Currently retrying a failed
export observer will re-export all export types, even if some already
succeeded, causing duplicate triggers.
Also there is a need to refine the terms for java identifiers (for example:
fields, classes) and documentation. Please document here a decision about what
we name different things. The term PCJ are the index tables used by Rya to
optimize it's queries. But sometimes it is used to describe the whole Fluo
framework. Please define a unique term for the following. The starred term
will be used here, but feel free to rename them:
- Rya query optimization PCJ (ex: the Blabla exporter) PCJ*
- Kafka trigger alert notifier (ex: the Foofoo exporter) Alerting*
- Fluo query observer framework (ex: results from the Barbar) FQF*
Unique identifers:
- FQF uses QueryID
- Alerting uses TopicID
- PCJ uses PcjId
Note that currently TopicID is assigned the same as QueryID, but that badly
presupposes queryID's cannot be grouped onto one Topic.
> Separate Fluo query result exporters, Rya PCJ intermingled kafka triggers
> -
>
> Key: RYA-246
> URL: https://issues.apache.org/jira/browse/RYA-246
> Project: Rya
> Issue Type: Improvement
> Components: dao
> Environment: Fluo, Kafka, PCJ, Accumulo
>Reporter: David W. Lotts
>
> Currently the Fluo query observer framework (FQF) has a great plugin-in-ish
> way of doing exports. (See field: {{exporters}} in class:
> {{org.apache.rya.indexing.pcj.fluo.app.observers.QueryResultObserver}} )
> Exports are query results and the action taken when they occur. Currently
> there are two. Despite this awesome framework, there are three
> interm
[jira] [Created] (RYA-246) Separate Fluo query result exporters, Rya PCJ intermingled kafka triggers
David W. Lotts created RYA-246:
--
Summary: Separate Fluo query result exporters, Rya PCJ
intermingled kafka triggers
Key: RYA-246
URL: https://issues.apache.org/jira/browse/RYA-246
Project: Rya
Issue Type: Improvement
Components: dao
Environment: Fluo, Kafka, PCJ, Accumulo
Reporter: David W. Lotts
Currently the Fluo query observer framework (FQF) has a great plugin-in-ish way
of doing exports. (See field: {{exporters}} in class:
{{org.apache.rya.indexing.pcj.fluo.app.observers.QueryResultObserver}} )
Exports are query results and the action taken when they occur. Currently
there are two. Despite this awsome framework, there are three interminglings
that can become issues in a production system:
1. Create PCJ independently of alerts/triggers
At query register time (with FQF), optionally create PCJ's and optionally
create alerts (with Alerting) preferably atomically, so if it fails in the
middle it does not leave dangling references and garbage -- currently there is
one method that does everything: CreatePCJ.withRyaInteraction()
2. Enable exporters per query -- currently all queries will be exported on all
globally enabled exporters
3. Separate export observer queues per exporter -- Currently retrying a failed
export observer will re-export all export types, even if some already
succeeded, causing duplicate triggers.
Also there is a need to refine the terms for java identifiers (for example:
fields, classes) and documentation. Please document here a decision about what
we name different things. The term PCJ are the index tables used by Rya to
optimize it's queries. But sometimes it is used to describe the whole Fluo
framework. Please define a unique term for the following. The starred term
will be used here, but feel free to rename them:
- Rya query optimization PCJ (ex: the Blabla exporter) PCJ*
- Kafka trigger alert notifier (ex: the Foofoo exporter) Alerting*
- Fluo query observer framework (ex: results from the Barbar) FQF*
Unique identifers:
- FQF uses QueryID
- Alerting uses TopicID
- PCJ uses PcjId
Note that currently TopicID is assigned the same as QueryID, but that badly
presupposes queryID's cannot be grouped onto one Topic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RYA-242) Geo function support in Fluo PCJ sparql queries
David W. Lotts created RYA-242: -- Summary: Geo function support in Fluo PCJ sparql queries Key: RYA-242 URL: https://issues.apache.org/jira/browse/RYA-242 Project: Rya Issue Type: New Feature Environment: Fluo PCJ Reporter: David W. Lotts Assignee: David W. Lotts Rya's Fluo pre-computed joins (PCJ) framework along with Kafka sub/pub gives makes Rya a strong Complex Event Processor (CEP) -- taking streaming input statements and generating results to subscribed (kafka topics) queries (PCJ's). We have identified geo functions as a major enabler for CEP users. Currently PCJ can handle basic SPARQL filter functions, but not geo functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
