[GitHub] [gora] djkevincr commented on a change in pull request #175: GORA-546 Hazelcast Jet execution engine support
djkevincr commented on a change in pull request #175: GORA-546 Hazelcast Jet execution engine support URL: https://github.com/apache/gora/pull/175#discussion_r392551036 ## File path: gora-tutorial/src/main/java/org/apache/gora/tutorial/log/LogAnalyticsJet.java ## @@ -0,0 +1,91 @@ +package org.apache.gora.tutorial.log; Review comment: Please add License header. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr commented on issue #175: GORA-546 Hazelcast Jet execution engine support
djkevincr commented on issue #175: GORA-546 Hazelcast Jet execution engine support URL: https://github.com/apache/gora/pull/175#issuecomment-599001808 @LahiruJayasekara Can you please resolve conflicts? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: Enabling Git workflow for Apache Gora
+1 On Fri, Mar 13, 2020 at 10:53 PM Madhawa Kasun Gunasekara < madhaw...@gmail.com> wrote: > Hi All, > > At the moment, when there is a new PR, we always have to build locally to > make sure the new PR doesn't introduce any regression issues. However, with > Github Actions, we can automate this effort with zero cost. I have written > a Github workflow to automatically build new PRs to check its validity. > > [1] https://github.com/apache/gora/pull/201 > > Thanks, > Madhawa >
[GitHub] [gora] madhawa-gunasekara merged pull request #203: Fix read me
madhawa-gunasekara merged pull request #203: Fix read me URL: https://github.com/apache/gora/pull/203 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr commented on issue #203: Fix read me
djkevincr commented on issue #203: Fix read me URL: https://github.com/apache/gora/pull/203#issuecomment-598884755 +1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] madhawa-gunasekara commented on issue #203: Fix read me
madhawa-gunasekara commented on issue #203: Fix read me URL: https://github.com/apache/gora/pull/203#issuecomment-598884500 @djkevincr done This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr commented on issue #203: Fix read me
djkevincr commented on issue #203: Fix read me URL: https://github.com/apache/gora/pull/203#issuecomment-598883842 @madhawa-gunasekara Can you please rebase against current master? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] madhawa-gunasekara opened a new pull request #203: Fix read me
madhawa-gunasekara opened a new pull request #203: Fix read me URL: https://github.com/apache/gora/pull/203 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr merged pull request #202: Disable Gora Kudu tests
djkevincr merged pull request #202: Disable Gora Kudu tests URL: https://github.com/apache/gora/pull/202 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr commented on issue #202: Disable Gora Kudu tests
djkevincr commented on issue #202: Disable Gora Kudu tests URL: https://github.com/apache/gora/pull/202#issuecomment-598881161 +1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] madhawa-gunasekara opened a new pull request #202: Disable Gora Kudu tests
madhawa-gunasekara opened a new pull request #202: Disable Gora Kudu tests URL: https://github.com/apache/gora/pull/202 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (GORA-644) Add Github Workflows for PR
[ https://issues.apache.org/jira/browse/GORA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059019#comment-17059019 ] Hudson commented on GORA-644: - FAILURE: Integrated in Jenkins build gora-trunk #1829 (See [https://builds.apache.org/job/gora-trunk/1829/]) GORA-644 (#201) (github: rev 736d457cd9ba1243858477c7218585858c70060c) * (add) .github/workflows/master-push-build.yml * (add) .github/workflows/master-pr-build.yml * (edit) README.md > Add Github Workflows for PR > --- > > Key: GORA-644 > URL: https://issues.apache.org/jira/browse/GORA-644 > Project: Apache Gora > Issue Type: Improvement >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It would be nice to have at least the source check running for each PR > possibly as a GitHub action -- This message was sent by Atlassian Jira (v8.3.4#803005)
gora-trunk - Build # 1829 - Still Failing
The Apache Jenkins build system has built gora-trunk (build #1829) Status: Still Failing Check console output at https://builds.apache.org/job/gora-trunk/1829/ to view the results.
[jira] [Updated] (GORA-271) Make consistent across datastores the way of getting the mapping filename
[ https://issues.apache.org/jira/browse/GORA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-271: --- Component/s: gora-hbase gora-dynamodb > Make consistent across datastores the way of getting the mapping filename > - > > Key: GORA-271 > URL: https://issues.apache.org/jira/browse/GORA-271 > Project: Apache Gora > Issue Type: Improvement > Components: gora-dynamodb, gora-hbase >Affects Versions: 0.3, 0.9 >Reporter: Apostolos Giannakidis >Assignee: Lahiru Jayasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > While working on GORA-231, I identified several datastores that do not use > the DataStoreFactory.getMappingFile() to retrieve the filename for the > mapping file from the properties file. These datastores are the following: > * gora-cassandra > * gora-dynamodb > * gora-hbase > I believe that this change will be a step forward towards having datastores > consistent to each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-271) Make consistent across datastores the way of getting the mapping filename
[ https://issues.apache.org/jira/browse/GORA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-271: --- Affects Version/s: 0.9 > Make consistent across datastores the way of getting the mapping filename > - > > Key: GORA-271 > URL: https://issues.apache.org/jira/browse/GORA-271 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.3, 0.9 >Reporter: Apostolos Giannakidis >Assignee: Lahiru Jayasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > While working on GORA-231, I identified several datastores that do not use > the DataStoreFactory.getMappingFile() to retrieve the filename for the > mapping file from the properties file. These datastores are the following: > * gora-cassandra > * gora-dynamodb > * gora-hbase > I believe that this change will be a step forward towards having datastores > consistent to each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GORA-271) Make consistent across datastores the way of getting the mapping filename
[ https://issues.apache.org/jira/browse/GORA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-271: -- Assignee: Lahiru Jayasekara (was: Apostolos Giannakidis) > Make consistent across datastores the way of getting the mapping filename > - > > Key: GORA-271 > URL: https://issues.apache.org/jira/browse/GORA-271 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.3 >Reporter: Apostolos Giannakidis >Assignee: Lahiru Jayasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > While working on GORA-231, I identified several datastores that do not use > the DataStoreFactory.getMappingFile() to retrieve the filename for the > mapping file from the properties file. These datastores are the following: > * gora-cassandra > * gora-dynamodb > * gora-hbase > I believe that this change will be a step forward towards having datastores > consistent to each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [gora] djkevincr merged pull request #170: GORA-271 Make consistent across datastores the way of getting the mapping filename
djkevincr merged pull request #170: GORA-271 Make consistent across datastores the way of getting the mapping filename URL: https://github.com/apache/gora/pull/170 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (GORA-644) Add Github Workflows for PR
[ https://issues.apache.org/jira/browse/GORA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhawa Kasun Gunasekara resolved GORA-644. --- Resolution: Fixed > Add Github Workflows for PR > --- > > Key: GORA-644 > URL: https://issues.apache.org/jira/browse/GORA-644 > Project: Apache Gora > Issue Type: Improvement >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It would be nice to have at least the source check running for each PR > possibly as a GitHub action -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-644) Add Github Workflows for PR
[ https://issues.apache.org/jira/browse/GORA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhawa Kasun Gunasekara updated GORA-644: -- Fix Version/s: 1.0 > Add Github Workflows for PR > --- > > Key: GORA-644 > URL: https://issues.apache.org/jira/browse/GORA-644 > Project: Apache Gora > Issue Type: Improvement >Reporter: Madhawa Kasun Gunasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It would be nice to have at least the source check running for each PR > possibly as a GitHub action -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GORA-644) Add Github Workflows for PR
[ https://issues.apache.org/jira/browse/GORA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhawa Kasun Gunasekara reassigned GORA-644: - Assignee: Madhawa Kasun Gunasekara > Add Github Workflows for PR > --- > > Key: GORA-644 > URL: https://issues.apache.org/jira/browse/GORA-644 > Project: Apache Gora > Issue Type: Improvement >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It would be nice to have at least the source check running for each PR > possibly as a GitHub action -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [gora] djkevincr merged pull request #200: Update developers list
djkevincr merged pull request #200: Update developers list URL: https://github.com/apache/gora/pull/200 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr merged pull request #201: GORA-644
djkevincr merged pull request #201: GORA-644 URL: https://github.com/apache/gora/pull/201 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [gora] djkevincr commented on issue #201: GORA-644
djkevincr commented on issue #201: GORA-644 URL: https://github.com/apache/gora/pull/201#issuecomment-598831556 +1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Enabling Git workflow for Apache Gora
Hi All, At the moment, when there is a new PR, we always have to build locally to make sure the new PR doesn't introduce any regression issues. However, with Github Actions, we can automate this effort with zero cost. I have written a Github workflow to automatically build new PRs to check its validity. [1] https://github.com/apache/gora/pull/201 Thanks, Madhawa
[GitHub] [gora] madhawa-gunasekara opened a new pull request #201: GORA-644
madhawa-gunasekara opened a new pull request #201: GORA-644 URL: https://github.com/apache/gora/pull/201 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (GORA-644) Add Github Workflows for PR
Madhawa Kasun Gunasekara created GORA-644: - Summary: Add Github Workflows for PR Key: GORA-644 URL: https://issues.apache.org/jira/browse/GORA-644 Project: Apache Gora Issue Type: Improvement Reporter: Madhawa Kasun Gunasekara It would be nice to have at least the source check running for each PR possibly as a GitHub action -- This message was sent by Atlassian Jira (v8.3.4#803005)
