[jira] [Resolved] (RYA-99) Integrate RyaDetails with PCJOptimizer
[ https://issues.apache.org/jira/browse/RYA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Chilton resolved RYA-99. -- Resolution: Done > 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] [Commented] (RYA-100) Update the build to us Maven animal-sniffer plugin.
[ https://issues.apache.org/jira/browse/RYA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388308#comment-15388308 ] ASF GitHub Bot commented on RYA-100: Github user kchilton2 commented on the issue: https://github.com/apache/incubator-rya/pull/54 Updated to use Java 8 signatures. > 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)
[GitHub] incubator-rya issue #54: RYA-100 Added Maven animal-sniffer plugin to build.
Github user kchilton2 commented on the issue: https://github.com/apache/incubator-rya/pull/54 Updated to use Java 8 signatures. --- 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-100) Update the build to us Maven animal-sniffer plugin.
[ https://issues.apache.org/jira/browse/RYA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388253#comment-15388253 ] ASF GitHub Bot commented on RYA-100: Github user kchilton2 commented on a diff in the pull request: https://github.com/apache/incubator-rya/pull/54#discussion_r71769754 --- Diff: pom.xml --- @@ -562,6 +562,29 @@ under the License. 1.7 + + + +org.codehaus.mojo +animal-sniffer-maven-plugin +1.15 + + +org.codehaus.mojo.signature +java17 --- End diff -- I'll update the signature to be for Java 1.8. > 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)
[GitHub] incubator-rya pull request #54: RYA-100 Added Maven animal-sniffer plugin to...
Github user kchilton2 commented on a diff in the pull request: https://github.com/apache/incubator-rya/pull/54#discussion_r71769754 --- Diff: pom.xml --- @@ -562,6 +562,29 @@ under the License. 1.7 + + + +org.codehaus.mojo +animal-sniffer-maven-plugin +1.15 + + +org.codehaus.mojo.signature +java17 --- End diff -- I'll update the signature to be for Java 1.8. --- 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] [Resolved] (RYA-98) InferenceEngine Configuration Issue in RyaDirectExample
[ https://issues.apache.org/jira/browse/RYA-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Meier resolved RYA-98. Resolution: Fixed > InferenceEngine Configuration Issue in RyaDirectExample > --- > > Key: RYA-98 > URL: https://issues.apache.org/jira/browse/RYA-98 > Project: Rya > Issue Type: Bug > Components: sail >Affects Versions: 3.2.10 >Reporter: Caleb Meier >Assignee: Caleb Meier >Priority: Minor > Fix For: 3.2.10 > > > Rya is currently configured to use inferencing by default. This shouldn't be > the case. Also, RyaDirectExample is not terminating because it creates an > instance of a SailRepository and a SailRepositoryConnection that it does not > close. By not closing the repository or the connection, the inference > engine, which is being created by default, does not get closed and the TImer > object within the Inference Engine causes the thread to be orphaned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RYA-115) Add Batch job commands to the Admin Shell
[ https://issues.apache.org/jira/browse/RYA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Meier updated RYA-115: Description: 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. (was: Fill this out.) > Add Batch job commands to the Admin Shell > - > > Key: RYA-115 > URL: https://issues.apache.org/jira/browse/RYA-115 > Project: Rya > Issue Type: Sub-task > Components: clients >Affects Versions: 3.2.10 >Reporter: Andrew Smith >Assignee: Caleb Meier > Fix For: 3.2.10 > > > 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-118) Query Based RDD
[ https://issues.apache.org/jira/browse/RYA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Meier updated RYA-118: Description: Add Spark Support to Rya providing capability to create RDDs from Rya queries. In particular, develop a factory which creates RDDs based on user specified entity-centric queries or statement patterns. > Query Based RDD > --- > > Key: RYA-118 > URL: https://issues.apache.org/jira/browse/RYA-118 > Project: Rya > Issue Type: Sub-task > Components: clients >Reporter: Andrew Smith >Assignee: Caleb Meier > Fix For: 3.2.10 > > > Add Spark Support to Rya providing capability to create RDDs from Rya > queries. In particular, develop a factory which creates RDDs based on user > specified entity-centric queries or statement patterns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-rya pull request #59: Adding a dynamo db backend for Rya
GitHub user pujav65 opened a pull request: https://github.com/apache/incubator-rya/pull/59 Adding a dynamo db backend for Rya You can merge this pull request into a Git repository by running: $ git pull https://github.com/pujav65/incubator-rya feature/dynamodb Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-rya/pull/59.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 #59 commit 40ad4df99c04b30bbd81dd458fac5232d709545e Author: pujav65 Date: 2016-06-23T15:59:05Z initial commit commit fbc13162654002687cad02b68b6eed38490ff634 Author: pujav65 Date: 2016-06-23T19:22:23Z interim checkin commit e30b29d0f98094cbda12c622a96581f38c337654 Author: pujav65 Date: 2016-06-24T02:45:24Z initial implementation commit cfeeac91907f2ebc60e0b04a7cb70d84b585af5b Author: pujav65 Date: 2016-07-08T12:30:25Z adding tests and mock support commit 353f992bc852cd1f38513f8fa1d58e599521f87b Author: pujav65 Date: 2016-06-23T15:59:05Z initial commit of dynamo db backend, adding tests and mock support commit 8303548b8da35eefc28c65d49a1d64bf377b36d2 Author: pujav65 Date: 2016-07-21T17:54:23Z fixing merge commit c0fdfcea91b757d36f650a90d935abd1f98e5b9f Author: pujav65 Date: 2016-07-21T18:11:59Z merging in develop --- 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] [Resolved] (RYA-105) Fluo Integration with Rya
[ https://issues.apache.org/jira/browse/RYA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Meier resolved RYA-105. - Resolution: Fixed > Fluo Integration with Rya > - > > Key: RYA-105 > URL: https://issues.apache.org/jira/browse/RYA-105 > Project: Rya > Issue Type: Bug > Components: dao >Affects Versions: 3.2.10 >Reporter: Caleb Meier >Assignee: Caleb Meier > Fix For: 3.2.10 > > > The Fluo table for incrementally updating precomputed joins is not fully > integrated with Rya. The PrecomputedJoinIndexer (which is an implementation > of the AccumuloIndexer interface) is not being added to the list of indexers > when the PCJ flag is set. So the DAO is never adding to Fluo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RYA-50) Add Support for Sparql Optional Statements in Precomputed Joins
[ https://issues.apache.org/jira/browse/RYA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Meier resolved RYA-50. Resolution: Fixed > Add Support for Sparql Optional Statements in Precomputed Joins > --- > > Key: RYA-50 > URL: https://issues.apache.org/jira/browse/RYA-50 > Project: Rya > Issue Type: Improvement >Affects Versions: 3.2.10 >Reporter: Caleb Meier >Assignee: Caleb Meier > Original Estimate: 60h > Remaining Estimate: 60h > > Rya currently only supports Precomputed Joins for SPARQL queries consisting > of StatementPatterns, Joins, and Filters. The task is to extend Rya's > Precomputed Join capability to allow for queries that contain OPTIONAL > statements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RYA-62) Query Optimization: Support more than one PCJ that has optional fields.
[ https://issues.apache.org/jira/browse/RYA-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Meier resolved RYA-62. Resolution: Fixed Fix Version/s: 3.2.10 > Query Optimization: Support more than one PCJ that has optional fields. > --- > > Key: RYA-62 > URL: https://issues.apache.org/jira/browse/RYA-62 > Project: Rya > Issue Type: New Feature >Reporter: Kevin Chilton >Assignee: Caleb Meier > Fix For: 3.2.10 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (RYA-99) Integrate RyaDetails with PCJOptimizer
[ https://issues.apache.org/jira/browse/RYA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Chilton reassigned RYA-99: Assignee: Caleb Meier (was: David W. Lotts) > 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)
incubator-rya-develop - Build # 21 - Aborted
The Apache Jenkins build system has built incubator-rya-develop (build #21) Status: Aborted Check console output at https://builds.apache.org/job/incubator-rya-develop/21/ to view the results.
[jira] [Commented] (RYA-105) Fluo Integration with Rya
[ https://issues.apache.org/jira/browse/RYA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387655#comment-15387655 ] ASF GitHub Bot commented on RYA-105: Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/58 merged > Fluo Integration with Rya > - > > Key: RYA-105 > URL: https://issues.apache.org/jira/browse/RYA-105 > Project: Rya > Issue Type: Bug > Components: dao >Affects Versions: 3.2.10 >Reporter: Caleb Meier >Assignee: Caleb Meier > Fix For: 3.2.10 > > > The Fluo table for incrementally updating precomputed joins is not fully > integrated with Rya. The PrecomputedJoinIndexer (which is an implementation > of the AccumuloIndexer interface) is not being added to the list of indexers > when the PCJ flag is set. So the DAO is never adding to Fluo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RYA-130) Rya Mongo Fail on Multi Bindingset Joins
[
https://issues.apache.org/jira/browse/RYA-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387657#comment-15387657
]
ASF GitHub Bot commented on RYA-130:
Github user pujav65 commented on the issue:
https://github.com/apache/incubator-rya/pull/57
merged
> 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
>
> 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)
[GitHub] incubator-rya issue #57: RYA-130 Fixed Rya Mongo Multi Binding Set Join
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/57 merged --- 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 #58: RYA-105: Fluo Integration
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/58 merged --- 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-105) Fluo Integration with Rya
[ https://issues.apache.org/jira/browse/RYA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387646#comment-15387646 ] ASF GitHub Bot commented on RYA-105: Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/58 again, lots of formatting changes so hard to figure out exactly what changed. It looks like the indexer was added to the factory, tests were fixed, and a few bugs in initialization were fixed (moving initialization to the init method, and changing to only write the version triple to the core tables). Looked fine to me -- I will merge. > Fluo Integration with Rya > - > > Key: RYA-105 > URL: https://issues.apache.org/jira/browse/RYA-105 > Project: Rya > Issue Type: Bug > Components: dao >Affects Versions: 3.2.10 >Reporter: Caleb Meier >Assignee: Caleb Meier > Fix For: 3.2.10 > > > The Fluo table for incrementally updating precomputed joins is not fully > integrated with Rya. The PrecomputedJoinIndexer (which is an implementation > of the AccumuloIndexer interface) is not being added to the list of indexers > when the PCJ flag is set. So the DAO is never adding to Fluo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-rya issue #58: RYA-105: Fluo Integration
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/58 again, lots of formatting changes so hard to figure out exactly what changed. It looks like the indexer was added to the factory, tests were fixed, and a few bugs in initialization were fixed (moving initialization to the init method, and changing to only write the version triple to the core tables). Looked fine to me -- I will merge. --- 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-130) Rya Mongo Fail on Multi Bindingset Joins
[
https://issues.apache.org/jira/browse/RYA-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387627#comment-15387627
]
ASF GitHub Bot commented on RYA-130:
Github user pujav65 commented on the issue:
https://github.com/apache/incubator-rya/pull/57
good catch -- about to merge. We should think about adding a correctness
test like what Jeff suggested.
> 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
>
> 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)
[GitHub] incubator-rya issue #56: Add Merge Tool
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/56 @amihalik did you have any other comments? Otherwise I was going to merge -- looked fine to me --- 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-76) Organize and document MapReduce support
[ https://issues.apache.org/jira/browse/RYA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387626#comment-15387626 ] ASF GitHub Bot commented on RYA-76: --- Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/55 merged > 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 > > 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)
[GitHub] incubator-rya issue #57: RYA-130 Fixed Rya Mongo Multi Binding Set Join
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/57 good catch -- about to merge. We should think about adding a correctness test like what Jeff suggested. --- 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 #55: RYA-76 Consolidated MapReduce API and applications ...
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/55 merged --- 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-76) Organize and document MapReduce support
[ https://issues.apache.org/jira/browse/RYA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387612#comment-15387612 ] ASF GitHub Bot commented on RYA-76: --- Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/55 looks good - about to merge > 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 > > 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)
[GitHub] incubator-rya issue #55: RYA-76 Consolidated MapReduce API and applications ...
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/55 looks good - about to merge --- 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-100) Update the build to us Maven animal-sniffer plugin.
[ https://issues.apache.org/jira/browse/RYA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387600#comment-15387600 ] ASF GitHub Bot commented on RYA-100: Github user pujav65 commented on a diff in the pull request: https://github.com/apache/incubator-rya/pull/54#discussion_r71696281 --- Diff: pom.xml --- @@ -562,6 +562,29 @@ under the License. 1.7 + + + +org.codehaus.mojo +animal-sniffer-maven-plugin +1.15 + + +org.codehaus.mojo.signature +java17 --- End diff -- I think a later pull request upgrades rya back to java 8 (an upgrade that was lost somehow when we ported to apache). Can you update this accordingly? Then I will merge. > 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)
[GitHub] incubator-rya pull request #54: RYA-100 Added Maven animal-sniffer plugin to...
Github user pujav65 commented on a diff in the pull request: https://github.com/apache/incubator-rya/pull/54#discussion_r71696281 --- Diff: pom.xml --- @@ -562,6 +562,29 @@ under the License. 1.7 + + + +org.codehaus.mojo +animal-sniffer-maven-plugin +1.15 + + +org.codehaus.mojo.signature +java17 --- End diff -- I think a later pull request upgrades rya back to java 8 (an upgrade that was lost somehow when we ported to apache). Can you update this accordingly? Then I will merge. --- 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 #53: Updated config to not use inferencing by default
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/53 merged --- 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 pull request #53: Updated config to not use inferencing by def...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-rya/pull/53 --- 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 #53: Updated config to not use inferencing by default
Github user pujav65 commented on the issue: https://github.com/apache/incubator-rya/pull/53 lots of reformatting -- maybe in the future try to avoid checking that stuff 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. ---
