[jira] [Closed] (RYA-30) Literal type information lost when inserting a matching literal with a different type

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-30.


> Literal type information lost when inserting a matching literal with a 
> different type
> -
>
> Key: RYA-30
> URL: https://issues.apache.org/jira/browse/RYA-30
> Project: Rya
>  Issue Type: Bug
>Reporter: Darren Griffith
>
>   I have 2 different SPARQL statements.  
>  
>   The first inserts a triple where the object is the integer literal "2" and 
> a triple where the object is the string literal "2".  I believe these should 
> be considered 2 different literals.  However, when I query for the triple 
> with the integer literal "2", it returns a triple with the string literal "2" 
> (see EXAMPLE 1).
>  
>   The second inserts only a triple where the object is the integer literal 
> "2", which is the same triple inserted by the first statement.  When I query 
> for this triple, it returns the triple with the integer literal "2" (see 
> EXAMPLE 2).
>  
>   I believe that my queries should return the same result in both cases.  It 
> seems the Rya isn't including the type information in the symbol table and 
> overwriting what should be different literals.
>  
> — EXAMPLE 1 — 
>  
> INSERT DATA {
>   
> 
>  
> "2"^^
>  .
> 
>   "2". 
> }
>  
>  
> SELECT *
> WHERE {
>  ?s  ?o .
> }    
>  
>  
> http://www.w3.org/2005/sparql-results#;>
> 
> 
> 
> 
> 
> 
> 
> 
> http://modusoperandi.com/Archivist/detection#jakarta_001.tif_jakarta_001_000.png
> 
> 
> 
> 2
> 
> 
> 
> 
>  
>  
>  
> — EXAMPLE 2 —
>  
> INSERT DATA {
>   
> 
>  
> "2"^^
>  .
> }
>  
> SELECT *
> WHERE {
>  ?s  ?o .
> }    
>  
> http://www.w3.org/2005/sparql-results#;>
> 
> 
> 
> 
> 
> 
> 
> 
> http://modusoperandi.com/Archivist/detection#jakarta_001.tif_jakarta_001_000.png
> 
> 
> 
> http://www.w3.org/2001/XMLSchema#integer;>2
> 
> 
> 
> 
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (RYA-23) RyaTripleContext should allow someone to get a TripllePatternStrategy for a given Layout

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik reopened RYA-23:
--

> RyaTripleContext should allow someone to get a TripllePatternStrategy for a 
> given Layout
> 
>
> Key: RYA-23
> URL: https://issues.apache.org/jira/browse/RYA-23
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> Right now there is not a standard way to easily translate between accumulo 
> keys and rya statements.  Exposing this at the RyaContext level will support 
> a RyaInputFormat well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-21) Rya Statements should have an input format and associated writable

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-21.

Resolution: Fixed

> Rya Statements should have an input format and associated writable
> --
>
> Key: RYA-21
> URL: https://issues.apache.org/jira/browse/RYA-21
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> There should be more guidance about how to integrate Rya with MapReduce.  We 
> have a statement output format and I thought we had an input format but I 
> couldn't find it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-2) Apache accouns for initial committers

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-2.
---

> Apache accouns for initial committers 
> --
>
> Key: RYA-2
> URL: https://issues.apache.org/jira/browse/RYA-2
> Project: Rya
>  Issue Type: Task
> Environment: setup
>Reporter: Adina Crainiceanu
>Assignee: Josh Elser
>
> Please create Apache accounts for the Rya incubator project initial 
> committers. All ICLAs have been submitted
> Committer -email used in ICLA - prefered Apache username
> David N Rapp dnr...@ncsu.edu  dnrapp
> -Steve Wagner steve.r.wag...@gmail.com swagner (I believe this account 
> already exists)-
> Aaron Mihalik aaron.miha...@gmail.com mihalik
> Jennifer Brown jennifer.br...@parsons.com jbrown
> Puja Valiyil puja...@gmail.compujav65
> Roshan Punnoose rosh...@gmail.com  roshanp
> Adina Crainiceanu adina...@gmail.com  adina 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-23) RyaTripleContext should allow someone to get a TripllePatternStrategy for a given Layout

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-23:
-
Fix Version/s: 3.2.10

> RyaTripleContext should allow someone to get a TripllePatternStrategy for a 
> given Layout
> 
>
> Key: RYA-23
> URL: https://issues.apache.org/jira/browse/RYA-23
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> Right now there is not a standard way to easily translate between accumulo 
> keys and rya statements.  Exposing this at the RyaContext level will support 
> a RyaInputFormat well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-21) Rya Statements should have an input format and associated writable

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-21:
-
Fix Version/s: 3.2.10

> Rya Statements should have an input format and associated writable
> --
>
> Key: RYA-21
> URL: https://issues.apache.org/jira/browse/RYA-21
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> There should be more guidance about how to integrate Rya with MapReduce.  We 
> have a statement output format and I thought we had an input format but I 
> couldn't find it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-96) Geo Indexer zookeeper dependency conflict.

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-96:
-
Fix Version/s: 3.2.10

> Geo Indexer zookeeper dependency conflict.
> --
>
> Key: RYA-96
> URL: https://issues.apache.org/jira/browse/RYA-96
> Project: Rya
>  Issue Type: Bug
> Environment: Integration test connected to an Accumulo instance 
> running on a cluster.
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
>Priority: Critical
> Fix For: 3.2.10
>
>
> The Accumulo implementation of the Geo Index does not work because of 
> conflicting zookeeper versions. It looks like Accumulo wants to use 3.3.6, so 
> that's what our build pulls in. However, GeoMesa depends on Curator which 
> uses zookeeper 3.4.6. This throws an exception when you try to initialize 
> Sail using a Geo Index.
> Stack Trace:
> java.lang.NoSuchMethodError: 
> org.apache.zookeeper.ZooKeeper.(Ljava/lang/String;ILorg/apache/zookeeper/Watcher;Z)V
>   at 
> org.apache.curator.utils.DefaultZookeeperFactory.newZooKeeper(DefaultZookeeperFactory.java:29)
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl$2.newZooKeeper(CuratorFrameworkImpl.java:146)
>   at org.apache.curator.HandleHolder$1.getZooKeeper(HandleHolder.java:94)
>   at org.apache.curator.HandleHolder.getZooKeeper(HandleHolder.java:55)
>   at org.apache.curator.ConnectionState.reset(ConnectionState.java:218)
>   at org.apache.curator.ConnectionState.start(ConnectionState.java:102)
>   at 
> org.apache.curator.CuratorZookeeperClient.start(CuratorZookeeperClient.java:189)
>   at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.start(CuratorFrameworkImpl.java:248)
>   at 
> org.locationtech.geomesa.accumulo.data.AccumuloDataStore.acquireDistributedLock(AccumuloDataStore.scala:806)
>   at 
> org.locationtech.geomesa.accumulo.data.AccumuloDataStore.createSchema(AccumuloDataStore.scala:264)
>   at 
> org.locationtech.geomesa.accumulo.data.AccumuloDataStore.createSchema(AccumuloDataStore.scala:65)
>   at 
> mvm.rya.indexing.accumulo.geo.GeoMesaGeoIndexer.getStatementFeatureType(GeoMesaGeoIndexer.java:226)
>   at 
> mvm.rya.indexing.accumulo.geo.GeoMesaGeoIndexer.initInternal(GeoMesaGeoIndexer.java:170)
>   at 
> mvm.rya.indexing.accumulo.geo.GeoMesaGeoIndexer.setConf(GeoMesaGeoIndexer.java:149)
>   at 
> org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:73)
>   at 
> org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:133)
>   at 
> org.apache.hadoop.conf.Configuration.getInstances(Configuration.java:1961)
>   at 
> mvm.rya.accumulo.AccumuloRdfConfiguration.getAdditionalIndexers(AccumuloRdfConfiguration.java:101)
>   at mvm.rya.accumulo.AccumuloRyaDAO.init(AccumuloRyaDAO.java:131)
>   at mvm.rya.sail.config.RyaSailFactory.getRyaSail(RyaSailFactory.java:82)
>   at 
> mvm.rya.sail.config.RyaSailFactory.getInstance(RyaSailFactory.java:50)
>   at 
> mvm.rya.indexing.accumulo.geo.GeoIndexerTest.test(GeoIndexerTest.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>   at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>   at 
> 

[jira] [Reopened] (RYA-76) Organize and document MapReduce support

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik reopened RYA-76:
--

> Organize and document MapReduce support
> ---
>
> Key: RYA-76
> URL: https://issues.apache.org/jira/browse/RYA-76
> Project: Rya
>  Issue Type: Improvement
>Reporter: Jesse Hatfield
>Assignee: Jesse Hatfield
> Fix For: 3.2.10
>
>
> Rya has some MapReduce support (e.g. a Writable, an InputFormat -- RYA-21), 
> but this could be more clearly structured and documented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-73) Add insert time to mongo backed rya

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-73:
-
Fix Version/s: 3.2.10

> Add insert time to mongo backed rya
> ---
>
> Key: RYA-73
> URL: https://issues.apache.org/jira/browse/RYA-73
> Project: Rya
>  Issue Type: Improvement
>Reporter: Andrew Smith
> Fix For: 3.2.10
>
>
> Some features of accumulo backed Rya require db insert time.  This is not 
> given for free in mongo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-78) RyaDirectExample throws UnsupportedOperationException becuase of ConditionalWriter

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-78:
-
Fix Version/s: 3.2.10

> RyaDirectExample throws UnsupportedOperationException becuase of 
> ConditionalWriter
> --
>
> Key: RYA-78
> URL: https://issues.apache.org/jira/browse/RYA-78
> Project: Rya
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 3.2.10
>Reporter: Caleb Meier
>Assignee: Caleb Meier
>Priority: Critical
> Fix For: 3.2.10
>
>
> Currently the RyaDirectExample throws an UnsupportedOperationException 
> because it uses a Mock Accumulo Instance and the class PcjTables, which 
> creates PCJs within the example, uses a ConditionalWriter on a Mock Accumulo 
> Table.  The example needs to be updated to use a MiniAccumuloCluster or the 
> PcjTables class needs to be configurable so that it can work with Mock 
> Accumulo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-76) Organize and document MapReduce support

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-76:
-
Fix Version/s: 3.2.10

> Organize and document MapReduce support
> ---
>
> Key: RYA-76
> URL: https://issues.apache.org/jira/browse/RYA-76
> Project: Rya
>  Issue Type: Improvement
>Reporter: Jesse Hatfield
>Assignee: Jesse Hatfield
> Fix For: 3.2.10
>
>
> Rya has some MapReduce support (e.g. a Writable, an InputFormat -- RYA-21), 
> but this could be more clearly structured and documented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-69) RyaDirectExample doesn't work on Mock Accumulo

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-69:
-
Fix Version/s: 3.2.10

> RyaDirectExample doesn't work on Mock Accumulo
> --
>
> Key: RYA-69
> URL: https://issues.apache.org/jira/browse/RYA-69
> Project: Rya
>  Issue Type: Bug
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Kevin Chilton
>Priority: Critical
> Fix For: 3.2.10
>
>
> This exception is thrown when running the RyaDirectExample:
> {code}
> Exception in thread "main" java.lang.UnsupportedOperationException
>   at 
> org.apache.accumulo.core.client.mock.MockConnector.createConditionalWriter(MockConnector.java:148)
>   at 
> mvm.rya.indexing.external.tupleSet.PcjTables.updateCardinality(PcjTables.java:659)
>   at 
> mvm.rya.indexing.external.tupleSet.PcjTables.addResults(PcjTables.java:564)
>   at 
> mvm.rya.indexing.external.tupleSet.PcjTables.populatePcj(PcjTables.java:767)
>   at 
> mvm.rya.indexing.external.tupleSet.PcjTables.createAndPopulatePcj(PcjTables.java:817)
>   at RyaDirectExample.createPCJ(RyaDirectExample.java:779)
>   at RyaDirectExample.main(RyaDirectExample.java:97)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (RYA-73) Add insert time to mongo backed rya

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik reopened RYA-73:
--

> Add insert time to mongo backed rya
> ---
>
> Key: RYA-73
> URL: https://issues.apache.org/jira/browse/RYA-73
> Project: Rya
>  Issue Type: Improvement
>Reporter: Andrew Smith
>
> Some features of accumulo backed Rya require db insert time.  This is not 
> given for free in mongo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-53) Add Visibility to Rya PCJs

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-53:
-
Fix Version/s: 3.2.10

> Add Visibility to Rya PCJs
> --
>
> Key: RYA-53
> URL: https://issues.apache.org/jira/browse/RYA-53
> Project: Rya
>  Issue Type: New Feature
>Reporter: Andrew Smith
>Assignee: Andrew Smith
> Fix For: 3.2.10
>
>
> Update the PCJ api to support visibility attached to binding sets



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-54) Rya vagrant script difficult to see failures

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-54.


> Rya vagrant script difficult to see failures
> 
>
> Key: RYA-54
> URL: https://issues.apache.org/jira/browse/RYA-54
> Project: Rya
>  Issue Type: Bug
>  Components: examples
> Environment: Rya in a VM
>Reporter: David W. Lotts
>Assignee: David W. Lotts
> Fix For: 3.2.10
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Rya example virtual machine is a wonderful way for new users to get up and 
> running fast and have a positive first experience with Rya.
> Several folks have attempted to create the Rya example virtual machine and 
> produce an unusable Rya instance on the first try.  They have no clue what 
> went wrong since they saw no errors and it appeared to complete successfully. 
>  Only when they attempt to use the web interface do they see errors.
> The relevent files are here:
> https://github.com/apache/incubator-rya/tree/develop/extras/vagrantExample/src/main/vagrant
> There are several reasons for this having to do with the {{Vagrant up}} 
> command that runs the Vagrantfile, a combination of vagrant specific syntax, 
> and Bash shell script:
> -  The curl download utility produces a nice progress output meant for a 
> terminal, but Vagrant  adds newlines so that it scrolls and fills up the 
> terminal buffer obscuring any errors messages that occur.  
> - Most failures are tolerated and allow the process to continue even when the 
> failure creates an unusable VM.   
> - Running the command {{vagrant provision}} is not idempotent.  When run more 
> than once, it should reset the configuration as it was installed, making it a 
> handy repair tool, however it generates false errors and fails.  Also, it 
> re-downloads very large files that are already present, making it no better 
> than starting over.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-65) Add Visibility Support to Fluo

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-65:
-
Fix Version/s: 3.2.10

> Add Visibility Support to Fluo
> --
>
> Key: RYA-65
> URL: https://issues.apache.org/jira/browse/RYA-65
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Andrew Smith
>Assignee: Andrew Smith
> Fix For: 3.2.10
>
>
> Add visibility support to Fluo:
> --When inserting to Fluo need to add a Visibility value.  We can't use the 
> visibility to the fluo visibility column since the visibility is on the 
> binding set, not fluo.
> --Ensure the visibility is applied to the binding set before being used 
> elsewhere



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-60) Update AccumuloIndexSet evaluate methods to scan for optional BindngSets

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-60:
-
Fix Version/s: 3.2.10

> Update AccumuloIndexSet evaluate methods to scan for optional BindngSets
> 
>
> Key: RYA-60
> URL: https://issues.apache.org/jira/browse/RYA-60
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Caleb Meier
>Assignee: Caleb Meier
> Fix For: 3.2.10
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-63) Add Visibility Support to accumulo PCJs

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-63.


> Add Visibility Support to accumulo PCJs
> ---
>
> Key: RYA-63
> URL: https://issues.apache.org/jira/browse/RYA-63
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Andrew Smith
>Assignee: Andrew Smith
> Fix For: 3.2.10
>
>
> Add support for visibility in accumulo PCJ tables:
> -When adding to a PCJ, add binding sets with visibility
> -Ensure that querying the PCJ table uses correct visibility



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-59) Update PrecompJoinOptimizer to support Sparql OPTIONAL statements

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-59:
-
Fix Version/s: 3.2.10

> Update PrecompJoinOptimizer to support Sparql OPTIONAL statements
> -
>
> Key: RYA-59
> URL: https://issues.apache.org/jira/browse/RYA-59
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Kevin Chilton
>Assignee: Caleb Meier
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-54) Rya vagrant script difficult to see failures

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-54:
-
Fix Version/s: 3.2.10

> Rya vagrant script difficult to see failures
> 
>
> Key: RYA-54
> URL: https://issues.apache.org/jira/browse/RYA-54
> Project: Rya
>  Issue Type: Bug
>  Components: examples
> Environment: Rya in a VM
>Reporter: David W. Lotts
>Assignee: David W. Lotts
> Fix For: 3.2.10
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Rya example virtual machine is a wonderful way for new users to get up and 
> running fast and have a positive first experience with Rya.
> Several folks have attempted to create the Rya example virtual machine and 
> produce an unusable Rya instance on the first try.  They have no clue what 
> went wrong since they saw no errors and it appeared to complete successfully. 
>  Only when they attempt to use the web interface do they see errors.
> The relevent files are here:
> https://github.com/apache/incubator-rya/tree/develop/extras/vagrantExample/src/main/vagrant
> There are several reasons for this having to do with the {{Vagrant up}} 
> command that runs the Vagrantfile, a combination of vagrant specific syntax, 
> and Bash shell script:
> -  The curl download utility produces a nice progress output meant for a 
> terminal, but Vagrant  adds newlines so that it scrolls and fills up the 
> terminal buffer obscuring any errors messages that occur.  
> - Most failures are tolerated and allow the process to continue even when the 
> failure creates an unusable VM.   
> - Running the command {{vagrant provision}} is not idempotent.  When run more 
> than once, it should reset the configuration as it was installed, making it a 
> handy repair tool, however it generates false errors and fails.  Also, it 
> re-downloads very large files that are already present, making it no better 
> than starting over.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-58) Add support to Fluo PCJ App for SPARQL OPTIONALs

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-58.


> Add support to Fluo PCJ App for SPARQL OPTIONALs
> 
>
> Key: RYA-58
> URL: https://issues.apache.org/jira/browse/RYA-58
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-56) Update BindingSetSerializer to write OPTIONAL BindingSets

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-56.


> Update BindingSetSerializer to write OPTIONAL BindingSets
> -
>
> Key: RYA-56
> URL: https://issues.apache.org/jira/browse/RYA-56
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-58) Add support to Fluo PCJ App for SPARQL OPTIONALs

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-58:
-
Fix Version/s: 3.2.10

> Add support to Fluo PCJ App for SPARQL OPTIONALs
> 
>
> Key: RYA-58
> URL: https://issues.apache.org/jira/browse/RYA-58
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-51) Temporal indexing support for MongoDB

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-51:
-
Fix Version/s: 3.2.10

> Temporal indexing support for MongoDB
> -
>
> Key: RYA-51
> URL: https://issues.apache.org/jira/browse/RYA-51
> Project: Rya
>  Issue Type: New Feature
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> There should be temporal indexing support for Mongo DB backed Rya.  i imagine 
> this would be implemented using another collection, similar to how temporal 
> indexing is implemented in Rya with a supplementary table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-45) Push down apache-rat configuration into each submodule

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-45:
-
Fix Version/s: 3.2.10

> Push down apache-rat configuration into each submodule
> --
>
> Key: RYA-45
> URL: https://issues.apache.org/jira/browse/RYA-45
> Project: Rya
>  Issue Type: Task
>  Components: build
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> There are a handful of apache rat "excludes" configuration in the parent pom, 
> and these should be pushed down to the submodules.
> The issue is that {{mvn clean install}} will apply these "excludes" 
> correctly, however {{mvn apache-rat:check}} will not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-45) Push down apache-rat configuration into each submodule

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-45.

Resolution: Fixed

> Push down apache-rat configuration into each submodule
> --
>
> Key: RYA-45
> URL: https://issues.apache.org/jira/browse/RYA-45
> Project: Rya
>  Issue Type: Task
>  Components: build
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> There are a handful of apache rat "excludes" configuration in the parent pom, 
> and these should be pushed down to the submodules.
> The issue is that {{mvn clean install}} will apply these "excludes" 
> correctly, however {{mvn apache-rat:check}} will not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-44) testMilliSecondsNoZone test case fails when running from +0530 time zone

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-44.


> testMilliSecondsNoZone test case fails when running from +0530 time zone
> 
>
> Key: RYA-44
> URL: https://issues.apache.org/jira/browse/RYA-44
> Project: Rya
>  Issue Type: Bug
>  Components: build
>Reporter: Amila Wijayarathna
>Assignee: Amila Wijayarathna
> Fix For: 3.2.10
>
>
>  I'm currently in +0530 time zone and when I build rya source with tests, 
> testMilliSecondsNoZone test fails with following output I'm currently in 
> +0530 time zone and when I build rya source with tests, 
> testMilliSecondsNoZone test fails with following output
> testMilliSecondsNoZone(mvm.rya.api.resolver.impl.DateTimeRyaTypeResolverTest)
>  Time elapsed: 0.051 sec  <<< FAILURE!
> java.lang.AssertionError: Before='2002-02-02T02:02:02.222'; Expected should
> match actual regex after='2002-02-02T\d\d:\d\d:02\.222Z'
> deserialized:2002-02-01T20:02:02.222Z
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> mvm.rya.api.resolver.impl.DateTimeRyaTypeResolverTest.testMilliSecondsNoZone(DateTimeRyaTypeResolverTest.java:116)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-19) Type-o in MongoDBRyaDAO

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-19:
-
Fix Version/s: 3.2.10

> Type-o in MongoDBRyaDAO
> ---
>
> Key: RYA-19
> URL: https://issues.apache.org/jira/browse/RYA-19
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.9
>Reporter: Jeff Dasch
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> Prevents a user from authenticating unless their password and db_name are the 
> same.
> At MongoDBRyaDAO.java:95
> Bug:
> MongoCredential cred = MongoCredential.createCredential(
> conf.get(MongoDBRdfConfiguration.MONGO_USER),
> conf.get(MongoDBRdfConfiguration.MONGO_USER_PASSWORD),
> conf.get(MongoDBRdfConfiguration.MONGO_DB_NAME).toCharArray());
> Fix:
> MongoCredential cred = MongoCredential.createCredential(
> conf.get(MongoDBRdfConfiguration.MONGO_USER),
> conf.get(MongoDBRdfConfiguration.MONGO_DB_NAME),
> conf.get(MongoDBRdfConfiguration.MONGO_USER_PASSWORD).toCharArray());



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-28) Secondary indexers should support a more involved life cycle

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-28:
-
Fix Version/s: 3.2.10

> Secondary indexers should support a more involved life cycle
> 
>
> Key: RYA-28
> URL: https://issues.apache.org/jira/browse/RYA-28
> Project: Rya
>  Issue Type: New Feature
>  Components: dao
>Reporter: Puja Valiyil 
> Fix For: 3.2.10
>
>
> There should be support for destroying, initializing, and dropping a 
> secondary index.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-28) Secondary indexers should support a more involved life cycle

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-28.


> Secondary indexers should support a more involved life cycle
> 
>
> Key: RYA-28
> URL: https://issues.apache.org/jira/browse/RYA-28
> Project: Rya
>  Issue Type: New Feature
>  Components: dao
>Reporter: Puja Valiyil 
> Fix For: 3.2.10
>
>
> There should be support for destroying, initializing, and dropping a 
> secondary index.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-19) Type-o in MongoDBRyaDAO

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-19.


> Type-o in MongoDBRyaDAO
> ---
>
> Key: RYA-19
> URL: https://issues.apache.org/jira/browse/RYA-19
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.9
>Reporter: Jeff Dasch
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> Prevents a user from authenticating unless their password and db_name are the 
> same.
> At MongoDBRyaDAO.java:95
> Bug:
> MongoCredential cred = MongoCredential.createCredential(
> conf.get(MongoDBRdfConfiguration.MONGO_USER),
> conf.get(MongoDBRdfConfiguration.MONGO_USER_PASSWORD),
> conf.get(MongoDBRdfConfiguration.MONGO_DB_NAME).toCharArray());
> Fix:
> MongoCredential cred = MongoCredential.createCredential(
> conf.get(MongoDBRdfConfiguration.MONGO_USER),
> conf.get(MongoDBRdfConfiguration.MONGO_DB_NAME),
> conf.get(MongoDBRdfConfiguration.MONGO_USER_PASSWORD).toCharArray());



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-4) Create RDF Tools Example with Persistent Data

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-4:

Fix Version/s: 3.2.10

> Create RDF Tools Example with Persistent Data
> -
>
> Key: RYA-4
> URL: https://issues.apache.org/jira/browse/RYA-4
> Project: Rya
>  Issue Type: Task
>  Components: examples
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> Currently, we have a handful of "mock accumulo" / in-memory examples of 
> loading data and querying Rya.  Also, we have instructions on deploying Rya 
> on an existing Accumulo cluster and interacting with Rya using a Java Client.
> This task is to create an example that allows users to get up and running on 
> Rya quickly and connecting to Rya using a common RDF stack.  Specifically, 
> this task will allow new users to persist data (using a docker or vagrant 
> instance of Accumulo) and connect to Rya using a common RDF tool (e.g. 
> Protege or the Sesame Web Application).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-6) DOA/Query Dates Test fail on Hortonworks Sandox

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-6:

Fix Version/s: 3.2.10

> DOA/Query Dates Test fail on Hortonworks Sandox
> ---
>
> Key: RYA-6
> URL: https://issues.apache.org/jira/browse/RYA-6
> Project: Rya
>  Issue Type: Bug
> Environment: OS: Hortonworks Sandbox with HDP 2.2.4 (Cent OS 6 64bit)
> Maven version: 3.3.3
> Java version: OpenJDK Runtime Environment 1.7.0_79
> Accumulo version: 1.6.1.2.2.4.2-2
> Hadoop version:2.6.0.2.2.4.2-2
>Reporter: Aaron Mihalik
>Assignee: David W. Lotts
> Fix For: 3.2.10
>
>
> here is the stack trace:
> {noformat}
> ---
> Test set: mvm.rya.accumulo.AccumuloRyaDAOTest
> ---
> Tests run: 19, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.243 sec 
> <<< FAILURE!
> testQueryDates(mvm.rya.accumulo.AccumuloRyaDAOTest)  Time elapsed: 0.16 sec  
> <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<1>
>   at org.junit.Assert.fail(Assert.java:91)
>   at org.junit.Assert.failNotEquals(Assert.java:645)
>   at org.junit.Assert.assertEquals(Assert.java:126)
>   at org.junit.Assert.assertEquals(Assert.java:470)
>   at org.junit.Assert.assertEquals(Assert.java:454)
>   at 
> mvm.rya.accumulo.AccumuloRyaDAOTest.testQueryDates(AccumuloRyaDAOTest.java:441)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-11) Free Text search support for Mongo DB backed Rya

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-11.


> Free Text search support for Mongo DB backed Rya
> 
>
> Key: RYA-11
> URL: https://issues.apache.org/jira/browse/RYA-11
> Project: Rya
>  Issue Type: New Feature
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> The secondary indexing support for Mongo DB should be extended to also 
> include support for free text search (which the Accumulo back end already 
> provides).  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-4) Create RDF Tools Example with Persistent Data

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-4.
---

> Create RDF Tools Example with Persistent Data
> -
>
> Key: RYA-4
> URL: https://issues.apache.org/jira/browse/RYA-4
> Project: Rya
>  Issue Type: Task
>  Components: examples
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> Currently, we have a handful of "mock accumulo" / in-memory examples of 
> loading data and querying Rya.  Also, we have instructions on deploying Rya 
> on an existing Accumulo cluster and interacting with Rya using a Java Client.
> This task is to create an example that allows users to get up and running on 
> Rya quickly and connecting to Rya using a common RDF stack.  Specifically, 
> this task will allow new users to persist data (using a docker or vagrant 
> instance of Accumulo) and connect to Rya using a common RDF tool (e.g. 
> Protege or the Sesame Web Application).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-6) DOA/Query Dates Test fail on Hortonworks Sandox

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-6.
---

> DOA/Query Dates Test fail on Hortonworks Sandox
> ---
>
> Key: RYA-6
> URL: https://issues.apache.org/jira/browse/RYA-6
> Project: Rya
>  Issue Type: Bug
> Environment: OS: Hortonworks Sandbox with HDP 2.2.4 (Cent OS 6 64bit)
> Maven version: 3.3.3
> Java version: OpenJDK Runtime Environment 1.7.0_79
> Accumulo version: 1.6.1.2.2.4.2-2
> Hadoop version:2.6.0.2.2.4.2-2
>Reporter: Aaron Mihalik
>Assignee: David W. Lotts
> Fix For: 3.2.10
>
>
> here is the stack trace:
> {noformat}
> ---
> Test set: mvm.rya.accumulo.AccumuloRyaDAOTest
> ---
> Tests run: 19, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.243 sec 
> <<< FAILURE!
> testQueryDates(mvm.rya.accumulo.AccumuloRyaDAOTest)  Time elapsed: 0.16 sec  
> <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<1>
>   at org.junit.Assert.fail(Assert.java:91)
>   at org.junit.Assert.failNotEquals(Assert.java:645)
>   at org.junit.Assert.assertEquals(Assert.java:126)
>   at org.junit.Assert.assertEquals(Assert.java:470)
>   at org.junit.Assert.assertEquals(Assert.java:454)
>   at 
> mvm.rya.accumulo.AccumuloRyaDAOTest.testQueryDates(AccumuloRyaDAOTest.java:441)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (RYA-130) Rya Mongo Fail on Multi Bindingset Joins

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik reopened RYA-130:
---

> Rya Mongo Fail on Multi Bindingset Joins
> 
>
> Key: RYA-130
> URL: https://issues.apache.org/jira/browse/RYA-130
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> Rya Mongo fails on a fairly straightforward query:
> {code}
> DATA = 
>  .
>  .
>  .
> QUERY = 
>   select ?s ?foo where { 
>   ?s  ?foo . 
>   ?s   }
> {code}
> This is a bug in how Mongo Rya solves joins.  The first Statement Pattern 
> will return multiple binding sets, and try to join it with a single 
> statement.  The Mongo Rya Query Engine can't handle this case.
> Full Code at: 
> https://gist.github.com/amihalik/61cf870650b7443389e7be7600f8502c



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-130) Rya Mongo Fail on Multi Bindingset Joins

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-130.
-
Resolution: Fixed

> Rya Mongo Fail on Multi Bindingset Joins
> 
>
> Key: RYA-130
> URL: https://issues.apache.org/jira/browse/RYA-130
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> Rya Mongo fails on a fairly straightforward query:
> {code}
> DATA = 
>  .
>  .
>  .
> QUERY = 
>   select ?s ?foo where { 
>   ?s  ?foo . 
>   ?s   }
> {code}
> This is a bug in how Mongo Rya solves joins.  The first Statement Pattern 
> will return multiple binding sets, and try to join it with a single 
> statement.  The Mongo Rya Query Engine can't handle this case.
> Full Code at: 
> https://gist.github.com/amihalik/61cf870650b7443389e7be7600f8502c



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-130) Rya Mongo Fail on Multi Bindingset Joins

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-130:
--
Fix Version/s: 3.2.10

> Rya Mongo Fail on Multi Bindingset Joins
> 
>
> Key: RYA-130
> URL: https://issues.apache.org/jira/browse/RYA-130
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> Rya Mongo fails on a fairly straightforward query:
> {code}
> DATA = 
>  .
>  .
>  .
> QUERY = 
>   select ?s ?foo where { 
>   ?s  ?foo . 
>   ?s   }
> {code}
> This is a bug in how Mongo Rya solves joins.  The first Statement Pattern 
> will return multiple binding sets, and try to join it with a single 
> statement.  The Mongo Rya Query Engine can't handle this case.
> Full Code at: 
> https://gist.github.com/amihalik/61cf870650b7443389e7be7600f8502c



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-102) MongoRyaDirect example is broken

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-102:
--
Fix Version/s: 3.2.10

> MongoRyaDirect example is broken
> 
>
> Key: RYA-102
> URL: https://issues.apache.org/jira/browse/RYA-102
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: David W. Lotts
>Priority: Blocker
> Fix For: 3.2.10
>
>
> Run the main method of the 'MongoRyaDirectExample' class.
> You will see the following exception:
> {code}
> Unable to create a connection to mongo.
> java.lang.NumberFormatException: null
> {code}
> I think that this probably broke around the time that we lost support for 
> mock/test mongo instances.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-157) RyaDirectExample fails on missing pcj.storageType

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-157:
--
Fix Version/s: 3.2.10

> RyaDirectExample fails on missing pcj.storageType
> -
>
> Key: RYA-157
> URL: https://issues.apache.org/jira/browse/RYA-157
> Project: Rya
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 3.2.9
>Reporter: David W. Lotts
>Assignee: David W. Lotts
>Priority: Blocker
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-157) RyaDirectExample fails on missing pcj.storageType

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-157.
-

> RyaDirectExample fails on missing pcj.storageType
> -
>
> Key: RYA-157
> URL: https://issues.apache.org/jira/browse/RYA-157
> Project: Rya
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 3.2.9
>Reporter: David W. Lotts
>Assignee: David W. Lotts
>Priority: Blocker
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-163) PCJDetails Test Failures on non-EST TimeZones

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-163.
-

> PCJDetails Test Failures on non-EST TimeZones
> -
>
> Key: RYA-163
> URL: https://issues.apache.org/jira/browse/RYA-163
> Project: Rya
>  Issue Type: Bug
> Environment: Apache Jenkins machine (UTC Timezone)
>Reporter: Aaron Mihalik
>Assignee: David W. Lotts
>Priority: Blocker
> Fix For: 3.2.10
>
>
> There are two tests failing on the build.  I think they are both due to a 
> timezone issue.
> I was able to reproduce these failures by setting my local timezone to 
> something other than eastern.
> https://builds.apache.org/job/incubator-rya-develop/27/testReport/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-173) rya.merger not creating signed version of bundle.zip

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-173:
--
Fix Version/s: 3.2.10

> rya.merger not creating signed version of bundle.zip
> 
>
> Key: RYA-173
> URL: https://issues.apache.org/jira/browse/RYA-173
> Project: Rya
>  Issue Type: Bug
>Reporter: Aaron Mihalik
>Assignee: Eric White
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-173) rya.merger not creating signed version of bundle.zip

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-173.
-

> rya.merger not creating signed version of bundle.zip
> 
>
> Key: RYA-173
> URL: https://issues.apache.org/jira/browse/RYA-173
> Project: Rya
>  Issue Type: Bug
>Reporter: Aaron Mihalik
>Assignee: Eric White
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-84) Add MongoDB support

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-84.


> Add MongoDB support
> ---
>
> Key: RYA-84
> URL: https://issues.apache.org/jira/browse/RYA-84
> Project: Rya
>  Issue Type: Sub-task
>Reporter: Andrew Smith
>Assignee: Andrew Smith
> Fix For: 3.2.10
>
>
> Implement DB connection interfaces with MongoDB



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-99) Integrate RyaDetails with PCJOptimizer

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-99.


> Integrate RyaDetails with PCJOptimizer
> --
>
> Key: RYA-99
> URL: https://issues.apache.org/jira/browse/RYA-99
> Project: Rya
>  Issue Type: Sub-task
>Affects Versions: 3.2.10
>Reporter: Caleb Meier
>Assignee: Caleb Meier
> Fix For: 3.2.10
>
>
> Update PCJOptimizer's "private static List 
> getAccIndices(Configuration conf)" method to use RyaDetailsRepository to 
> fetch the names of the PCJs that may be used.
> Currently it looks in the configuration file to find all of the PCJ tables 
> that will be used. If it doesn't find them, then we iterate through the 
> tables and try to find them programatically. We're moving away from that 
> strategy. Instead, we should look at the instance's Rya details to find all 
> of the PCJ IDs that are being maintained, then derive the table names from 
> those. This means we no longer need to iterate through all the tables to find 
> them using table operations.
> If there are no rya details for the specified instance of Rya, use the old 
> method.
> Here is the file to update:
> https://github.com/kchilton2/incubator-rya/blob/RYA-81/extras/indexing/src/main/java/mvm/rya/indexing/pcj/matching/PCJOptimizer.java
> The factory for making the tables names is here:
> PcjTableNameFactory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-107) Use RyaDetails table to Configure PrecomputedJoinUpdaters for PrecomputedJoinIndexer

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-107.
-

> Use RyaDetails table to Configure PrecomputedJoinUpdaters for 
> PrecomputedJoinIndexer
> 
>
> Key: RYA-107
> URL: https://issues.apache.org/jira/browse/RYA-107
> Project: Rya
>  Issue Type: Sub-task
>  Components: dao
>Affects Versions: 3.2.10
>Reporter: Caleb Meier
>Assignee: Caleb Meier
> Fix For: 3.2.10
>
>
> Currently Rya has only one update strategy for PrecomputedJoins, which is to 
> use Fluo.  A Batch and a No_Update strategy need to implemented and 
> integrated with the PrecomputedJoinIndexer.  The PrecomputedJoinIndexer 
> should use the RyaDetails table to determine which update strategy to use - 
> if at least one table for the Rya instance requires either a Fluo or Batch 
> update strategy, then the PrecomputedJoinIndexer should utilize those 
> updaters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-32) Improve how metadata and values are written to Accumulo PCJ tables.

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-32.


> Improve how metadata and values are written to Accumulo PCJ tables.
> ---
>
> Key: RYA-32
> URL: https://issues.apache.org/jira/browse/RYA-32
> Project: Rya
>  Issue Type: Improvement
>Reporter: Kevin Chilton
>Assignee: Caleb Meier
> Fix For: 3.2.10
>
>
> Refactor how Precomputed Joins (PCJs) are stored in Accumulo.
> 1. Change how PCJ results are written to an Accumulo PCJ table so that they 
> include all information required to deserialize them.
> 2. Change how the PCJ metadata is stored within the Accumulo table to allow 
> Cardinalities to be updated.
> 3. Create an API for interacting with PCJ tables.
> 4. Update the accmulo.pig project to write values using the new formats.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-100) Update the build to us Maven animal-sniffer plugin.

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-100.
-

> Update the build to us Maven animal-sniffer plugin.
> ---
>
> Key: RYA-100
> URL: https://issues.apache.org/jira/browse/RYA-100
> Project: Rya
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.2.10
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>
> Rya uses Java 1.7. If you are compiling on a machine using a 1.8 JDK, though, 
> the build succeeds when Java 1.8 features are used within the source. This is 
> a problem the animal-sniffer plugin fixes. Hook animal-sniffer:check into the 
> test phase of the build so that it will list where Java 1.8+ features are 
> being used and fail the build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-37) Bump GeoMesa version to 1.2.0

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-37.


> Bump GeoMesa version to 1.2.0
> -
>
> Key: RYA-37
> URL: https://issues.apache.org/jira/browse/RYA-37
> Project: Rya
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.2.10
>Reporter: Mike Pfaffenberger
> Fix For: 3.2.10
>
>
> GeoMesa is released officially. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-35) BindingSet String Serialization

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-35.


> BindingSet String Serialization
> ---
>
> Key: RYA-35
> URL: https://issues.apache.org/jira/browse/RYA-35
> Project: Rya
>  Issue Type: Improvement
>Affects Versions: 3.2.9
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>
> Create a class that serializes sesame BindingSet objects to a String and back 
> again. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-25) Apache RAT check during maven build

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-25.


> Apache RAT check during maven build
> ---
>
> Key: RYA-25
> URL: https://issues.apache.org/jira/browse/RYA-25
> Project: Rya
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.2.9
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
>Priority: Minor
> Fix For: 3.2.10
>
>
> Currently Apache-RAT doesn't run during a {{mvn clean install}} and has to be 
> run as a separate {{mvn apache-rat:check}}.  This should be part of the 
> default maven lifecycle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-103) Upgrade Rya back to java 8

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-103.
-

> Upgrade Rya back to java 8
> --
>
> Key: RYA-103
> URL: https://issues.apache.org/jira/browse/RYA-103
> Project: Rya
>  Issue Type: Bug
>Reporter: Puja Valiyil 
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>
> At some point during the port to apache, we lost the upgrade of Rya to Java 
> 8.  This should involve just updating the pom to reference 1.8 for the 
> compiler level instead of 1.7.  When we did this before, no code changes had 
> to take place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-114) Command that lets a new user access the Rya Accumulo tables.

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-114:
--
Fix Version/s: (was: 3.2.10)

> Command that lets a new user access the Rya Accumulo tables.
> 
>
> Key: RYA-114
> URL: https://issues.apache.org/jira/browse/RYA-114
> Project: Rya
>  Issue Type: Improvement
>  Components: clients
>Affects Versions: 3.2.10
>Reporter: Andrew Smith
>
> Need a Create User command that creates a new user and supplies the 
> appropriate permissions to the various tables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-119) Add visibility support to MongoDB

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-119:
--
Fix Version/s: (was: 3.2.10)

> Add visibility support to MongoDB
> -
>
> Key: RYA-119
> URL: https://issues.apache.org/jira/browse/RYA-119
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Affects Versions: 3.2.10
>Reporter: Andrew Smith
>
> Currently, when querying mongo, visibility is ignored.  Need to add support 
> for visibility when querying mongo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-131) Use RyaDetails in PcjUpdaterSupplierFactory

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-131:
--
Fix Version/s: (was: 3.2.10)

> Use RyaDetails in PcjUpdaterSupplierFactory
> ---
>
> Key: RYA-131
> URL: https://issues.apache.org/jira/browse/RYA-131
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Affects Versions: 3.2.10
>Reporter: Caleb Meier
>Assignee: Kevin Chilton
>
> Currently PcjUpdaterSupplierFactory relies on user configuration to determine 
> the updating strategies for the PrecomputedJoinIndexer.  Instead it should 
> retrieve the updater strategies from RyaDetails by scanning the PCJ details 
> for all of the Rya instance PCJ ids to see if any are configured to be 
> updated via Fluo. Also, any configuration constants and accessor methods that 
> have been added to manage the retrieval of user updater strategies from the 
> config should be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-142) Update to Apache Fluo 1.0.0-incubating

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-142:
--
Fix Version/s: (was: 3.2.10)

> Update to Apache Fluo 1.0.0-incubating
> --
>
> Key: RYA-142
> URL: https://issues.apache.org/jira/browse/RYA-142
> Project: Rya
>  Issue Type: Improvement
>Affects Versions: 3.2.10
>Reporter: Keith Turner
>Assignee: Kevin Chilton
>
> Once Apache Fluo 1.0.0-incubating is released (hopefully that will happen in 
> the next few weeks) RYA can be updated to use those.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-14) Upgrade to Java 1.7

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-14.


> Upgrade to Java 1.7
> ---
>
> Key: RYA-14
> URL: https://issues.apache.org/jira/browse/RYA-14
> Project: Rya
>  Issue Type: New Feature
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-104) Mongo Support in Rya Administrative Shell

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-104:
--
Fix Version/s: (was: 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.10
>Reporter: Andrew Smith
>Assignee: Andrew Smith
>
> Implement mongo support for the admin shell.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-109) Add Spark support

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-109:
--
Fix Version/s: (was: 3.2.10)

> 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.10
>Reporter: Andrew Smith
>Assignee: Evan Good
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-111) Add Browse commands to Admin Shell

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-111:
--
Fix Version/s: (was: 3.2.10)

> Add Browse commands to Admin Shell
> --
>
> Key: RYA-111
> URL: https://issues.apache.org/jira/browse/RYA-111
> Project: Rya
>  Issue Type: New Feature
>  Components: clients
>Affects Versions: 3.2.10
>Reporter: Andrew Smith
>Priority: Minor
>
> Browse statements
> execute query
> Load statement
> load statements from file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-115) Add Batch job commands to the Admin Shell

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-115:
--
Fix Version/s: (was: 3.2.10)

> Add Batch job commands to the Admin Shell
> -
>
> Key: RYA-115
> URL: https://issues.apache.org/jira/browse/RYA-115
> Project: Rya
>  Issue Type: New Feature
>  Components: clients
>Affects Versions: 3.2.10
>Reporter: Andrew Smith
>Priority: Minor
>
> Add commands to the Admin Shell run prospector and join selectivity batch 
> jobs. Other batch options might include inconsistency detection and batch 
> updates of PCJs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-123) Mongo Support in the Merge Tool

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-123:
--
Fix 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
>Affects Versions: 3.2.10
>Reporter: Andrew Smith
>Assignee: Andrew Smith
>
> 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.3.4#6332)

[jira] [Closed] (RYA-143) Upgrade Mongo to 3.0

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-143.
-

> Upgrade Mongo to 3.0
> 
>
> Key: RYA-143
> URL: https://issues.apache.org/jira/browse/RYA-143
> Project: Rya
>  Issue Type: New Feature
>  Components: dao
>Affects Versions: 3.2.10
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-121) Store contextual metadata for individual triples

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-121:
--
Fix Version/s: (was: 3.2.10)

> 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 
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-147) Fluo PCJ Updater - Delete Statement Support

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-147:
--
Fix Version/s: (was: 3.2.10)

> Fluo PCJ Updater - Delete Statement Support
> ---
>
> Key: RYA-147
> URL: https://issues.apache.org/jira/browse/RYA-147
> Project: Rya
>  Issue Type: New Feature
>Affects Versions: 3.2.10
>Reporter: Kevin Chilton
>
> The Fluo PCJ Updater application currently only allows you to add new 
> statements to generated PCJs. We would also like to be able to delete 
> statements from the end results.
> Here is a simple example to illustrate the point. Suppose you are computing 
> the following SPARQL query as a PCJ:
> {code}
> SELECT * 
> WHERE {
> ?person   .
> }
> {code}
> And you insert the following Statements:
> {code}
> {
> [, , ],
> [, , ],
> [, , ]
> }
> {code}
> The PCJ will result in the following binding sets:
> {code}
> {
> [], 
> [], 
> []
> }
> {code}
> We should also be able to delete the following statement:
> {code}
> [, , ]
> {code}
> And the PCJ should be updated to contain the following results:
> {code}
> {
> [], 
> []
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-3) Move rya.manual docs into markdown

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-3.
---

> Move rya.manual docs into markdown
> --
>
> Key: RYA-3
> URL: https://issues.apache.org/jira/browse/RYA-3
> Project: Rya
>  Issue Type: Task
>  Components: docs
>Reporter: Aaron Mihalik
>Assignee: Aaron Mihalik
>Priority: Trivial
> Fix For: 3.2.10
>
>
> Most of the Rya documentation is in the rya.manual project.  It would be more 
> accessible if it was re-written using github flavored markdown, directories 
> re-structured in a conventional way, and linked to from the main readme.md 
> file.
> This task isn't so much about the content or correctness of the 
> documentation.  It's more about the format and directory structure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-20) Mongo indices are redundant

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-20.


> Mongo indices are redundant
> ---
>
> Key: RYA-20
> URL: https://issues.apache.org/jira/browse/RYA-20
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.9
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
> Fix For: 3.2.10
>
>
> The subject, predicate, object indices are redundant with the composite 
> indices.  They should be deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RYA-49) Update vagrant file to use accumulo version 1.6.5

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-49.

Resolution: Fixed

> Update vagrant file to use accumulo version 1.6.5
> -
>
> Key: RYA-49
> URL: https://issues.apache.org/jira/browse/RYA-49
> Project: Rya
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 3.2.10
>Reporter: Eric White
>Assignee: David W. Lotts
>Priority: Minor
> Fix For: 3.2.10
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-145) Entity Centric Index throws exception if user has no authorizations.

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-145:
--
Fix Version/s: (was: 3.2.10)

> Entity Centric Index throws exception if user has no authorizations.
> 
>
> Key: RYA-145
> URL: https://issues.apache.org/jira/browse/RYA-145
> Project: Rya
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 3.2.10
>Reporter: Kevin Chilton
>Assignee: Caleb Meier
>
> To replicate:
> Use a rya client that connects to an Accumulo backend (mock or real; both 
> replicate this bug) and provide an empty string as the authorizations for the 
> user within the Rya configuration object.
> You should see the following exception:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: Empty 
> authorization
>   at 
> org.apache.accumulo.core.security.Authorizations.checkAuths(Authorizations.java:95)
>   at 
> org.apache.accumulo.core.security.Authorizations.setAuthorizations(Authorizations.java:195)
>   at 
> org.apache.accumulo.core.security.Authorizations.(Authorizations.java:184)
>   at 
> mvm.rya.indexing.accumulo.entity.AccumuloDocIdIndexer.runQuery(AccumuloDocIdIndexer.java:424)
>   at 
> mvm.rya.indexing.accumulo.entity.AccumuloDocIdIndexer.access$1(AccumuloDocIdIndexer.java:401)
>   at 
> mvm.rya.indexing.accumulo.entity.AccumuloDocIdIndexer$2.hasNext(AccumuloDocIdIndexer.java:275)
>   at 
> info.aduna.iteration.ConvertingIteration.hasNext(ConvertingIteration.java:73)
>   at 
> mvm.rya.rdftriplestore.RdfCloudTripleStoreConnection$1.hasNext(RdfCloudTripleStoreConnection.java:405)
>   at 
> info.aduna.iteration.IterationWrapper.hasNext(IterationWrapper.java:68)
>   at 
> org.openrdf.sail.helpers.SailBaseIteration.hasNext(SailBaseIteration.java:61)
>   at 
> info.aduna.iteration.IterationWrapper.hasNext(IterationWrapper.java:68)
>   at 
> org.apache.rya.indexing.pcj.storage.accumulo.PcjTables.populatePcj(PcjTables.java:567)
>   at 
> org.apache.rya.indexing.pcj.storage.accumulo.PcjTables.createAndPopulatePcj(PcjTables.java:627)
>   at RyaDirectExample.createPCJ(RyaDirectExample.java:816)
>   at RyaDirectExample.main(RyaDirectExample.java:107)
> {code}
> Expected Behavior:
> The application should process the request using the empty authorizations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-132) Fluo PCJ Updater - The app doesn't export correctly.

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-132:
--
Fix Version/s: (was: 3.2.10)

> Fluo PCJ Updater - The app doesn't export correctly.
> 
>
> Key: RYA-132
> URL: https://issues.apache.org/jira/browse/RYA-132
> Project: Rya
>  Issue Type: Bug
>Affects Versions: 3.2.10
>Reporter: Kevin Chilton
>Assignee: Kevin Chilton
>Priority: Minor
>
> The RyaResultsExporter is not written correctly. It assumes a single thread 
> will perform the export, which is not the case. This results in cardinality 
> values that are higher than they should be.
> The following Fluo recipe explains how to safely export from Fluo:
> https://github.com/apache/incubator-fluo-recipes/blob/master/docs/export-queue.md
> That recipe will only guarantee that a single transaction will be used to 
> write the results to to the Export Queue. However, the Exporter you write may 
> be executed on many machine concurrently, so you still may get many out of 
> order and duplicated exports. The PrecomputedJoinStorage.addResults(...) 
> method needs to be updated to handle that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-49) Update vagrant file to use accumulo version 1.6.5

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-49:
-
Fix Version/s: (was: 3.2.10)

> Update vagrant file to use accumulo version 1.6.5
> -
>
> Key: RYA-49
> URL: https://issues.apache.org/jira/browse/RYA-49
> Project: Rya
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 3.2.10
>Reporter: Eric White
>Assignee: David W. Lotts
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-154) Decouple Configuration for Using PCJs and Using PCJ updater

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-154:
--
Fix 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
>Affects Versions: 3.2.10
>Reporter: Caleb Meier
>Assignee: Caleb Meier
>
> 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.3.4#6332)

[jira] [Updated] (RYA-126) Refactor Accumulo functionality in new interfaces

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-126:
--
Fix Version/s: (was: 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
>
> Re-implement accumulo functionality with new interfaces.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-127) Implement mongo functionality

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-127:
--
Fix Version/s: (was: 3.2.10)

> Implement 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
>
> Implement Cloning/Merging functionality in Mongo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-141) Copy Tool - Accumulo Support

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-141:
--
Fix Version/s: (was: 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
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RYA-161) Integrate Mongo and Accumulo in a client

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-161:
--
Fix Version/s: (was: 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
>
> 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.3.4#6332)

incubator-rya-master - Build # 32 - Still Unstable

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-rya-master (build #32)

Status: Still Unstable

Check console output at https://builds.apache.org/job/incubator-rya-master/32/ 
to view the results.

[jira] [Resolved] (RYA-173) rya.merger not creating signed version of bundle.zip

[Eric White (JIRA)]

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

Eric White resolved RYA-173.

Resolution: Fixed

> rya.merger not creating signed version of bundle.zip
> 
>
> Key: RYA-173
> URL: https://issues.apache.org/jira/browse/RYA-173
> Project: Rya
>  Issue Type: Bug
>Reporter: Aaron Mihalik
>Assignee: Eric White
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RYA-173) rya.merger not creating signed version of bundle.zip

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on RYA-173:


Github user asfgit closed the pull request at:

https://github.com/apache/incubator-rya/pull/88


> rya.merger not creating signed version of bundle.zip
> 
>
> Key: RYA-173
> URL: https://issues.apache.org/jira/browse/RYA-173
> Project: Rya
>  Issue Type: Bug
>Reporter: Aaron Mihalik
>Assignee: Eric White
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-rya pull request #88: RYA-173 Fixed signing of rya.merger distribu...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-rya/pull/88


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-rya issue #88: RYA-173 Fixed signing of rya.merger distribution zi...

[amihalik]

Github user amihalik commented on the issue:

https://github.com/apache/incubator-rya/pull/88
  
Looks good.  I'm going to test it out.  If it works, I'll pull it in and 
cut an RC2


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (RYA-172) Rya Merger Test Fail (persists temp data between test)

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-172:
--
Assignee: Eric White  (was: Puja Valiyil )

> Rya Merger Test Fail (persists temp data between test)
> --
>
> Key: RYA-172
> URL: https://issues.apache.org/jira/browse/RYA-172
> Project: Rya
>  Issue Type: Bug
>Reporter: Aaron Mihalik
>Assignee: Eric White
>
> CopyToolTest.testImportDirectoryTool will fail the second time it's run.  
> There is data hanging around in  /tmp/hadoop-amihalik/ (for me) after the 
> first run of the test and it's causing issues the second time.
> To reproduce:
> in incubator-rya, build rya:
> {code}
> mvn clean install -DskipTests
> {code}
> now run the rya.merger tests a couple times:
> {code}
> cd extras/rya.merger
> mvn clean install
> mvn clean install
> {code}
> The error should be this on the second time through
> {code}
> CopyToolTest.testImportDirectoryTool:355 expected:<20> but was:<0>
> {code}
> This was in my log (in eclispe):
> {code}
> 2016-09-07 18:16:44,752 ERROR [main] merge.CopyTool 
> (CopyTool.java:setupAndRun(860)) - Error running copy tool
> java.io.IOException: Target 
> /tmp/hadoop-mihalik/copy_tool_import/ct_spo/ct_spo is a directory
> {code}
> my work around is to 
> {code}
> rm -rf /tmp/hadoop-mihalik/
> {code}
> between tests



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-rya pull request #88: RYA-173 Fixed signing of rya.merger distribu...

[ejwhite922]

GitHub user ejwhite922 opened a pull request:

https://github.com/apache/incubator-rya/pull/88

RYA-173 Fixed signing of rya.merger distribution zip.  Added Apache l…

…icenses to rya.merger and rya.indexing.example distribution zips.

## Description
Fixed rya.merger-bundle.zip signature issue when building.  Also, added 
Apache licenses to the distribution zips for the rya.merger and 
rya.indexing.example projects.

### Tests
Ran build to generate the zips and verified the licenses appeared.

### Links
[Jira](https://issues.apache.org/jira/browse/RYA-173)

### Checklist
- [x] Code Review
- [ ] Squash Commits

 People To Review
@amihalik 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ejwhite922/incubator-rya 
RYA-173_MergerSignedBundle

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-rya/pull/88.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #88


commit 23eb369c89b875d8576c4568b777c1d698dfc3f6
Author: eric.white 
Date:   2016-09-08T19:22:21Z

RYA-173 Fixed signing of rya.merger distribution zip.  Added Apache 
licences to rya.merger and rya.indexing.example distribution zips.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Closed] (RYA-171) Mongo Tests are not Cleaning up

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik closed RYA-171.
-
Resolution: Duplicate

> Mongo Tests are not Cleaning up
> ---
>
> Key: RYA-171
> URL: https://issues.apache.org/jira/browse/RYA-171
> Project: Rya
>  Issue Type: Bug
>Reporter: Aaron Mihalik
>Assignee: Puja Valiyil 
>Priority: Blocker
>
> The Mongo Test seem to be keeping the Embeded Mongo open and hogging a port.  
> See test fails here:
> https://builds.apache.org/job/incubator-rya-master/31/org.apache.rya$rya.indexing/
> and 
> https://builds.apache.org/job/incubator-rya-master/30/org.apache.rya$rya.indexing/
> I don't quite this issue, because there were no changes for builds 30 and 31 
> (these are manual builds that I kicked off).
> https://builds.apache.org/job/incubator-rya-master/30/
> This is blocking a release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (RYA-174) Embedded Mongo tries to bind to busy ports

[Aaron Mihalik (JIRA)]

Aaron Mihalik created RYA-174:
-

 Summary: Embedded Mongo tries to bind to busy ports
 Key: RYA-174
 URL: https://issues.apache.org/jira/browse/RYA-174
 Project: Rya
  Issue Type: Bug
Reporter: Aaron Mihalik
Assignee: David W. Lotts


There are a couple mongo tests that fail while building on builds.a.o.  It 
looks like Embedded Mongo will try to bind to ports that are already in use.


https://builds.apache.org/view/Incubator%20Projects/job/incubator-rya-master/org.apache.rya$rya.indexing/31/testReport/junit/mvm.rya.indexing.mongo/MongoGeoIndexerSfTest/testIntersectsLine/

https://builds.apache.org/view/Incubator%20Projects/job/incubator-rya-master/org.apache.rya$rya.indexing/31/testReport/junit/mvm.rya.indexing.mongo/MongoTemporalIndexerTest/testQueryInstantHasBeginningInterval/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)