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

[Puja Valiyil (JIRA)]

Puja Valiyil  created RYA-21:


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


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)

[GitHub] incubator-rya pull request: RYA-17, RYA-19, RYA-20 issue with mong...

[amihalik]

Github user amihalik commented on the pull request:

https://github.com/apache/incubator-rya/pull/6#issuecomment-165796392
  
Looks good.  I'll pull it in.


---
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] [Created] (RYA-22) MongoDBRyaDAO silently throws exceptions

[Aaron Mihalik (JIRA)]

Aaron Mihalik created RYA-22:


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


{{MongoDBRyaDAO}} throws a handful of exceptions during init.  These exceptions 
should probably be re-thrown as  {{RyaDAOException}}



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

[jira] [Commented] (RYA-17) Mongo DAO layer can't handle wildcard deletes

[ASF GitHub Bot (JIRA)]

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

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

Github user amihalik commented on the pull request:

https://github.com/apache/incubator-rya/pull/6#issuecomment-165796392
  
Looks good.  I'll pull it in.


> Mongo DAO layer can't handle wildcard deletes
> -
>
> Key: RYA-17
> URL: https://issues.apache.org/jira/browse/RYA-17
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.10
>Reporter: Christian Rasmussen
>Assignee: Puja Valiyil 
>
> When requesting a delete using wildcards for either Predicate, Object or 
> Context we fail with a null pointer exception.
> [DEBUG] 2015-12-15 00:05:06,341 [repositories/rya] subj=""
> [DEBUG] 2015-12-15 00:05:06,348 [repositories/rya] 
> ProtocolExceptionResolver.resolveException() called
> [ERROR] 2015-12-15 00:05:06,352 [repositories/rya] Error while handling 
> request
> java.lang.NullPointerException: null
>   at 
> mvm.rya.mongodb.dao.SimpleMongoDBStorageStrategy.serialize(SimpleMongoDBStorageStrategy.java:104)
>   at mvm.rya.mongodb.MongoDBRyaDAO.delete(MongoDBRyaDAO.java:110)
>   at mvm.rya.mongodb.MongoDBRyaDAO.delete(MongoDBRyaDAO.java:1)
>   at 
> mvm.rya.rdftriplestore.RdfCloudTripleStoreConnection.removeStatementsInternal(RdfCloudTripleStoreConnection.java:513)
>   at 
> org.openrdf.sail.helpers.SailConnectionBase.removeStatements(SailConnectionBase.java:495)
>   at 
> org.openrdf.repository.sail.SailRepositoryConnection.removeWithoutCommit(SailRepositoryConnection.java:296)
> For this example,  the only thing I specified in my delete request is the 
> 'subj="”’ 
> Dumping out the RYAStatement content here:
> RyaStatement{subject=RyaType{dataType=http://www.w3.org/2001/XMLSchema#anyURI,
>  data='http://tempuri.org'}, predicate=null, object=null, context=null, 
> qualifier=null, columnVisibility=null, value=null, timestamp=1450155906348}
> This then fails in the SimpleMongoDBStorageStrategy.serialize() because we 
> are trying to concatenate a bunch of fields to create the id (type String) 
> String id = statement.getSubject().getData() + " " +
> statement.getPredicate().getData() + " " +
> statement.getObject().getData() + " " +
> context;
> As an aside. We do not allow subject wildcard. This appears to be deliberate 
> and due to performance issues. However that seems like a feature that should 
> support as well.



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

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

[Puja Valiyil (JIRA)]

Puja Valiyil  created RYA-23:


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


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)

[GitHub] incubator-rya pull request: RYA-17, RYA-19, RYA-20 issue with mong...

[amihalik]

Github user amihalik commented on the pull request:

https://github.com/apache/incubator-rya/pull/6#issuecomment-165798435
  
You added a new file (`MongoDBRyaDAOTest.java`) and it doesn't have a 
license header (so it failed `mvn apache-rat:check`).  Please go back in and 
add the header, then I'll pull in this PR.


---
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] [Commented] (RYA-17) Mongo DAO layer can't handle wildcard deletes

[ASF GitHub Bot (JIRA)]

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

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

Github user amihalik commented on the pull request:

https://github.com/apache/incubator-rya/pull/6#issuecomment-165798435
  
You added a new file (`MongoDBRyaDAOTest.java`) and it doesn't have a 
license header (so it failed `mvn apache-rat:check`).  Please go back in and 
add the header, then I'll pull in this PR.


> Mongo DAO layer can't handle wildcard deletes
> -
>
> Key: RYA-17
> URL: https://issues.apache.org/jira/browse/RYA-17
> Project: Rya
>  Issue Type: Bug
>  Components: dao
>Affects Versions: 3.2.10
>Reporter: Christian Rasmussen
>Assignee: Puja Valiyil 
>
> When requesting a delete using wildcards for either Predicate, Object or 
> Context we fail with a null pointer exception.
> [DEBUG] 2015-12-15 00:05:06,341 [repositories/rya] subj=""
> [DEBUG] 2015-12-15 00:05:06,348 [repositories/rya] 
> ProtocolExceptionResolver.resolveException() called
> [ERROR] 2015-12-15 00:05:06,352 [repositories/rya] Error while handling 
> request
> java.lang.NullPointerException: null
>   at 
> mvm.rya.mongodb.dao.SimpleMongoDBStorageStrategy.serialize(SimpleMongoDBStorageStrategy.java:104)
>   at mvm.rya.mongodb.MongoDBRyaDAO.delete(MongoDBRyaDAO.java:110)
>   at mvm.rya.mongodb.MongoDBRyaDAO.delete(MongoDBRyaDAO.java:1)
>   at 
> mvm.rya.rdftriplestore.RdfCloudTripleStoreConnection.removeStatementsInternal(RdfCloudTripleStoreConnection.java:513)
>   at 
> org.openrdf.sail.helpers.SailConnectionBase.removeStatements(SailConnectionBase.java:495)
>   at 
> org.openrdf.repository.sail.SailRepositoryConnection.removeWithoutCommit(SailRepositoryConnection.java:296)
> For this example,  the only thing I specified in my delete request is the 
> 'subj="”’ 
> Dumping out the RYAStatement content here:
> RyaStatement{subject=RyaType{dataType=http://www.w3.org/2001/XMLSchema#anyURI,
>  data='http://tempuri.org'}, predicate=null, object=null, context=null, 
> qualifier=null, columnVisibility=null, value=null, timestamp=1450155906348}
> This then fails in the SimpleMongoDBStorageStrategy.serialize() because we 
> are trying to concatenate a bunch of fields to create the id (type String) 
> String id = statement.getSubject().getData() + " " +
> statement.getPredicate().getData() + " " +
> statement.getObject().getData() + " " +
> context;
> As an aside. We do not allow subject wildcard. This appears to be deliberate 
> and due to performance issues. However that seems like a feature that should 
> support as well.



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

[jira] [Created] (RYA-24) Rya Hashing based triple pattern strategy does not support regex filters

[Puja Valiyil (JIRA)]

Puja Valiyil  created RYA-24:


 Summary: Rya Hashing based triple pattern strategy does not 
support regex filters
 Key: RYA-24
 URL: https://issues.apache.org/jira/browse/RYA-24
 Project: Rya
  Issue Type: Improvement
  Components: dao
Reporter: Puja Valiyil 
Assignee: Puja Valiyil 


There is a bug within the hashing storage strategy that does not support regex 
filters.



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

"newbie" label on Jira Issues

[Aaron D. Mihalik]

Puja and I were discussing having issues in JIRA that are pretty
straightforward to fix and would provide a good way to get new developers'
feet wet on the code base.

I looked at the Accumulo JIRA and it seems like they label this as 'newbie'
issues.  I think we should adopt this convention as well and I've started
using it.

For example: https://issues.apache.org/jira/browse/RYA-22

It's fairly easy to search by label in JIRA.  But here's a link for all of
the open "newbie" issues for Rya:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20RYA%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20newbie

--Aaron

Re: "newbie" label on Jira Issues

[Adina Crainiceanu]

Aaron,

Great idea. Could you update the confluence wiki with this information, as
I think it would be useful for new contributors?

Thanks,
Adina

On Fri, Dec 18, 2015 at 10:10 AM, Aaron D. Mihalik 
wrote:

> Puja and I were discussing having issues in JIRA that are pretty
> straightforward to fix and would provide a good way to get new developers'
> feet wet on the code base.
>
> I looked at the Accumulo JIRA and it seems like they label this as 'newbie'
> issues.  I think we should adopt this convention as well and I've started
> using it.
>
> For example: https://issues.apache.org/jira/browse/RYA-22
>
> It's fairly easy to search by label in JIRA.  But here's a link for all of
> the open "newbie" issues for Rya:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20RYA%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20newbie
>
> --Aaron
>



-- 
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/

new notifications mailing list created - please subscribe if interested

[Adina Crainiceanu]

All,

As we voted earlier, a new mailing list was created to handle automatic
notifications from JIRA and possible other automatic notifications. If
interested in receiving these notifications, please send an email to
notifications-subscr...@rya.incubator.apache.org

I plan on changing the settings for JIRA on Monday to send the
notifications to the new list instead of dev@r.i.a.o.

dev@r.i.a.o will NO LONGER receive automatic notifications from JIRA after
Monday.


Thank you,
Adina

-- 
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/

[jira] [Commented] (RYA-24) Rya Hashing based triple pattern strategy does not support regex filters

[ASF GitHub Bot (JIRA)]

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

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

GitHub user pujav65 opened a pull request:

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

RYA-24 issue with hashes and regex queries



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

$ git pull https://github.com/pujav65/incubator-rya RYA-24

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

https://github.com/apache/incubator-rya/pull/7.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 #7


commit d6635321e4dcd6a29c15e850a065c74f2d946bf9
Author: pujav65 
Date:   2015-12-18T15:52:18Z

RYA-24 issue with hashes and regex queries




> Rya Hashing based triple pattern strategy does not support regex filters
> 
>
> Key: RYA-24
> URL: https://issues.apache.org/jira/browse/RYA-24
> Project: Rya
>  Issue Type: Improvement
>  Components: dao
>Reporter: Puja Valiyil 
>Assignee: Puja Valiyil 
>
> There is a bug within the hashing storage strategy that does not support 
> regex filters.



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

[GitHub] incubator-rya pull request: RYA-24 issue with hashes and regex que...

[pujav65]

GitHub user pujav65 opened a pull request:

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

RYA-24 issue with hashes and regex queries



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

$ git pull https://github.com/pujav65/incubator-rya RYA-24

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

https://github.com/apache/incubator-rya/pull/7.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 #7


commit d6635321e4dcd6a29c15e850a065c74f2d946bf9
Author: pujav65 
Date:   2015-12-18T15:52:18Z

RYA-24 issue with hashes and regex queries




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

Re: "newbie" label on Jira Issues

[Josh Elser]

+1

Adina Crainiceanu wrote:

Aaron,

Great idea. Could you update the confluence wiki with this information, as
I think it would be useful for new contributors?

Thanks,
Adina

On Fri, Dec 18, 2015 at 10:10 AM, Aaron D. Mihalik
wrote:


Puja and I were discussing having issues in JIRA that are pretty
straightforward to fix and would provide a good way to get new developers'
feet wet on the code base.

I looked at the Accumulo JIRA and it seems like they label this as 'newbie'
issues.  I think we should adopt this convention as well and I've started
using it.

For example: https://issues.apache.org/jira/browse/RYA-22

It's fairly easy to search by label in JIRA.  But here's a link for all of
the open "newbie" issues for Rya:


https://issues.apache.org/jira/issues/?jql=project%20%3D%20RYA%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20newbie

--Aaron

[jira] [Updated] (RYA-16) Build and Deploy to ASF and Maven Central Repository

[Aaron Mihalik (JIRA)]

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

Aaron Mihalik updated RYA-16:
-
Component/s: build

> Build and Deploy to ASF and Maven Central Repository 
> -
>
> Key: RYA-16
> URL: https://issues.apache.org/jira/browse/RYA-16
> Project: Rya
>  Issue Type: Task
>  Components: build
>Affects Versions: 3.2.10
> Environment: Rya project's pom.xml, repository.apache.org,  
> repo1.maven.org/maven2
>Reporter: David W. Lotts
>  Labels: build, maven
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Setup all the required configuration, permissions, and keys for deploying 
> releases to the ASF snapshot and release repositories, which synchronizes to 
> the Central Repository.



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

[jira] [Created] (RYA-25) Apaach RAT check during maven build

[Aaron Mihalik (JIRA)]

Aaron Mihalik created RYA-25:


 Summary: Apaach 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
Priority: Minor


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] [Updated] (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 updated RYA-25:
-
Summary: Apache RAT check during maven build  (was: Apaach RAT check during 
maven build)

> 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
>Priority: Minor
>
> 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)

[GitHub] incubator-rya pull request: RYA-25 Apache RAT check during maven b...

[amihalik]

GitHub user amihalik opened a pull request:

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

RYA-25 Apache RAT check during maven build

Modified the parent POM so that the Apache RAT plugin runs by default;
modified log4j properties for blueprints to put temp log in target;
removed extraneous shading.

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

$ git pull https://github.com/amihalik/incubator-rya RYA-25

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

https://github.com/apache/incubator-rya/pull/8.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 #8


commit 1eae9015ede1a95a881fd3bc26476a244695e030
Author: Aaron Mihalik 
Date:   2015-12-18T20:24:13Z

RYA-25 Apache RAT check during maven build

Modified the parent POM so that the Apache RAT plugin runs by default;
modified log4j properties for blueprints to put temp log in target;
removed extraneous shading.




---
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] [Commented] (RYA-25) Apache RAT check during maven build

[ASF GitHub Bot (JIRA)]

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

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

GitHub user amihalik opened a pull request:

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

RYA-25 Apache RAT check during maven build

Modified the parent POM so that the Apache RAT plugin runs by default;
modified log4j properties for blueprints to put temp log in target;
removed extraneous shading.

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

$ git pull https://github.com/amihalik/incubator-rya RYA-25

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

https://github.com/apache/incubator-rya/pull/8.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 #8


commit 1eae9015ede1a95a881fd3bc26476a244695e030
Author: Aaron Mihalik 
Date:   2015-12-18T20:24:13Z

RYA-25 Apache RAT check during maven build

Modified the parent POM so that the Apache RAT plugin runs by default;
modified log4j properties for blueprints to put temp log in target;
removed extraneous shading.




> 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
>Priority: Minor
>
> 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)