[jira] [Created] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to run queries
Israel Herraiz created BEAM-8458: Summary: BigQueryIO.Read needs permissions to create datasets to run queries Key: BEAM-8458 URL: https://issues.apache.org/jira/browse/BEAM-8458 Project: Beam Issue Type: Bug Components: io-java-gcp Reporter: Israel Herraiz When using `fromQuery`, BigQueryIO creates a temp dataset to store the results of the query. Therefore, Beam requires permissions to create datasets just to be able to run a query. In practice, this means that Beam requires the role bigQuery.User just to run queries, whereas if you use `from` (to read from a table), the role bigQuery.jobUser suffices. BigQueryIO.Read should have an option to set an existing dataset to write the temp results of a query, so it would be enough with having the role bigQuery.jobUser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to run queries
[ https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-8458: Assignee: Israel Herraiz > BigQueryIO.Read needs permissions to create datasets to run queries > --- > > Key: BEAM-8458 > URL: https://issues.apache.org/jira/browse/BEAM-8458 > Project: Beam > Issue Type: Bug > Components: io-java-gcp >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > When using `fromQuery`, BigQueryIO creates a temp dataset to store the > results of the query. > Therefore, Beam requires permissions to create datasets just to be able to > run a query. In practice, this means that Beam requires the role > bigQuery.User just to run queries, whereas if you use `from` (to read from a > table), the role bigQuery.jobUser suffices. > BigQueryIO.Read should have an option to set an existing dataset to write > the temp results of > a query, so it would be enough with having the role bigQuery.jobUser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-8458:
-
Description:
When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
results of the query.
Therefore, Beam requires permissions to create datasets just to be able to run
a query. In practice, this means that Beam requires the role bigQuery.User just
to run queries, whereas if you use {{from}} (to read from a table), the role
bigQuery.jobUser suffices.
BigQueryIO.Read should have an option to set an existing dataset to write the
temp results of
a query, so it would be enough with having the role bigQuery.jobUser.
was:
When using `fromQuery`, BigQueryIO creates a temp dataset to store the results
of the query.
Therefore, Beam requires permissions to create datasets just to be able to run
a query. In practice, this means that Beam requires the role bigQuery.User just
to run queries, whereas if you use `from` (to read from a table), the role
bigQuery.jobUser suffices.
BigQueryIO.Read should have an option to set an existing dataset to write the
temp results of
a query, so it would be enough with having the role bigQuery.jobUser.
> BigQueryIO.Read needs permissions to create datasets to run queries
> ---
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-8458:
-
Summary: BigQueryIO.Read needs permissions to create datasets to be able to
run queries (was: BigQueryIO.Read needs permissions to create datasets to run
queries)
> BigQueryIO.Read needs permissions to create datasets to be able to run queries
> --
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-8458:
-
Fix Version/s: 2.20.0
> BigQueryIO.Read needs permissions to create datasets to be able to run queries
> --
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Fix For: Not applicable, 2.20.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-8458:
-
Fix Version/s: (was: Not applicable)
> BigQueryIO.Read needs permissions to create datasets to be able to run queries
> --
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Fix For: 2.20.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-8458:
-
Fix Version/s: (was: 2.20.0)
2.21.0
> BigQueryIO.Read needs permissions to create datasets to be able to run queries
> --
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045952#comment-17045952
]
Israel Herraiz commented on BEAM-8458:
--
Pull request merged
> BigQueryIO.Read needs permissions to create datasets to be able to run queries
> --
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (BEAM-8458) BigQueryIO.Read needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz resolved BEAM-8458.
--
Fix Version/s: Not applicable
Resolution: Fixed
> BigQueryIO.Read needs permissions to create datasets to be able to run queries
> --
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: Major
> Fix For: Not applicable
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp dataset to store the
> results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigQueryIO.Read should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (BEAM-10018) Windowing katas are failing because timestamps are being calculated in local timezones
Israel Herraiz created BEAM-10018: - Summary: Windowing katas are failing because timestamps are being calculated in local timezones Key: BEAM-10018 URL: https://issues.apache.org/jira/browse/BEAM-10018 Project: Beam Issue Type: Bug Components: katas Affects Versions: 2.20.0 Reporter: Israel Herraiz Fix For: 2.21.0 The two Python katas about windowing fail because the timestamps for the elements are calculated based on the local timezone, and my timezone does not match the timezone hardcoded in the tests. I am working on a pull request to set the timezones in UTC, so the tests are always done in UTC, and the timestamps are always set in UTC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (BEAM-10018) Windowing katas are failing because timestamps are being calculated in local timezones
[ https://issues.apache.org/jira/browse/BEAM-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-10018: - Assignee: Israel Herraiz > Windowing katas are failing because timestamps are being calculated in local > timezones > -- > > Key: BEAM-10018 > URL: https://issues.apache.org/jira/browse/BEAM-10018 > Project: Beam > Issue Type: Bug > Components: katas >Affects Versions: 2.20.0 >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.21.0 > > > The two Python katas about windowing fail because the timestamps for the > elements are calculated based on the local timezone, and my timezone does not > match the timezone hardcoded in the tests. > I am working on a pull request to set the timezones in UTC, so the tests are > always done in UTC, and the timestamps are always set in UTC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-10018) Windowing katas are failing because timestamps are being calculated in local timezones
[ https://issues.apache.org/jira/browse/BEAM-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-10018: -- Status: Open (was: Triage Needed) > Windowing katas are failing because timestamps are being calculated in local > timezones > -- > > Key: BEAM-10018 > URL: https://issues.apache.org/jira/browse/BEAM-10018 > Project: Beam > Issue Type: Bug > Components: katas >Affects Versions: 2.20.0 >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.21.0 > > > The two Python katas about windowing fail because the timestamps for the > elements are calculated based on the local timezone, and my timezone does not > match the timezone hardcoded in the tests. > I am working on a pull request to set the timezones in UTC, so the tests are > always done in UTC, and the timestamps are always set in UTC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (BEAM-10018) Windowing katas are failing because timestamps are being calculated in local timezones
[ https://issues.apache.org/jira/browse/BEAM-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz resolved BEAM-10018. --- Resolution: Fixed > Windowing katas are failing because timestamps are being calculated in local > timezones > -- > > Key: BEAM-10018 > URL: https://issues.apache.org/jira/browse/BEAM-10018 > Project: Beam > Issue Type: Bug > Components: katas >Affects Versions: 2.20.0 >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.21.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > The two Python katas about windowing fail because the timestamps for the > elements are calculated based on the local timezone, and my timezone does not > match the timezone hardcoded in the tests. > I am working on a pull request to set the timezones in UTC, so the tests are > always done in UTC, and the timestamps are always set in UTC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (BEAM-13836) Python katas answer placeholders with wrong locations
Israel Herraiz created BEAM-13836: - Summary: Python katas answer placeholders with wrong locations Key: BEAM-13836 URL: https://issues.apache.org/jira/browse/BEAM-13836 Project: Beam Issue Type: Bug Components: katas Reporter: Israel Herraiz The answers of the Python katas are misplace because of the changes (tagging text) added with BEAM-13395. The katas don't work well now with the Edu plugin of PyCharm. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (BEAM-13836) Python katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-13836: - Assignee: Israel Herraiz > Python katas answer placeholders with wrong locations > - > > Key: BEAM-13836 > URL: https://issues.apache.org/jira/browse/BEAM-13836 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > > The answers of the Python katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of PyCharm. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (BEAM-13836) Python katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487752#comment-17487752 ] Israel Herraiz commented on BEAM-13836: --- I am working in a fix to this. It requires going kata per kata, and recalculating the position of the placeholders. > Python katas answer placeholders with wrong locations > - > > Key: BEAM-13836 > URL: https://issues.apache.org/jira/browse/BEAM-13836 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > > The answers of the Python katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of PyCharm. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (BEAM-14093) OffsetRestrictionTracker calculates wrongly the tryClaim conditions
Israel Herraiz created BEAM-14093:
-
Summary: OffsetRestrictionTracker calculates wrongly the tryClaim
conditions
Key: BEAM-14093
URL: https://issues.apache.org/jira/browse/BEAM-14093
Project: Beam
Issue Type: Bug
Components: io-py-common
Affects Versions: 2.37.0
Reporter: Israel Herraiz
The OffsetRestrictionTracker method tryClaim tries to calculate if the claim
can be done using this condition:
{code:python}
if self._range.start <= position < self._range.stop:
self._current_position = position
return True{code}
The condition should be
{code:python}
if self._range.start <= position and position < self._range.stop:
self._current_position = position
return True{code}
This affects the correctness of the claims for SplittableDoFns.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (BEAM-14093) OffsetRestrictionTracker calculates wrongly the tryClaim conditions
[
https://issues.apache.org/jira/browse/BEAM-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz reassigned BEAM-14093:
-
Assignee: Israel Herraiz
> OffsetRestrictionTracker calculates wrongly the tryClaim conditions
> ---
>
> Key: BEAM-14093
> URL: https://issues.apache.org/jira/browse/BEAM-14093
> Project: Beam
> Issue Type: Bug
> Components: io-py-common
>Affects Versions: 2.37.0
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: P1
>
> The OffsetRestrictionTracker method tryClaim tries to calculate if the claim
> can be done using this condition:
> {code:python}
> if self._range.start <= position < self._range.stop:
> self._current_position = position
> return True{code}
> The condition should be
> {code:python}
> if self._range.start <= position and position < self._range.stop:
> self._current_position = position
> return True{code}
> This affects the correctness of the claims for SplittableDoFns.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (BEAM-14093) OffsetRestrictionTracker calculates wrongly the tryClaim conditions
[
https://issues.apache.org/jira/browse/BEAM-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-14093:
--
Fix Version/s: Not applicable
Resolution: Invalid
Status: Resolved (was: Triage Needed)
It turns out you can chain comparisons in Python:
https://www.geeksforgeeks.org/chaining-comparison-operators-python/
> OffsetRestrictionTracker calculates wrongly the tryClaim conditions
> ---
>
> Key: BEAM-14093
> URL: https://issues.apache.org/jira/browse/BEAM-14093
> Project: Beam
> Issue Type: Bug
> Components: io-py-common
>Affects Versions: 2.37.0
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: P1
> Fix For: Not applicable
>
>
> The OffsetRestrictionTracker method tryClaim tries to calculate if the claim
> can be done using this condition:
> {code:python}
> if self._range.start <= position < self._range.stop:
> self._current_position = position
> return True{code}
> The condition should be
> {code:python}
> if self._range.start <= position and position < self._range.stop:
> self._current_position = position
> return True{code}
> This affects the correctness of the claims for SplittableDoFns.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (BEAM-13923) Java katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490864#comment-17490864 ] Israel Herraiz commented on BEAM-13923: --- Working on a fix to the placeholders locations. > Java katas answer placeholders with wrong locations > --- > > Key: BEAM-13923 > URL: https://issues.apache.org/jira/browse/BEAM-13923 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > > The answers of the Java katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (BEAM-13923) Java katas answer placeholders with wrong locations
Israel Herraiz created BEAM-13923: - Summary: Java katas answer placeholders with wrong locations Key: BEAM-13923 URL: https://issues.apache.org/jira/browse/BEAM-13923 Project: Beam Issue Type: Bug Components: katas Reporter: Israel Herraiz The answers of the Java katas are misplace because of the changes (tagging text) added with BEAM-13395. The katas don't work well now with the Edu plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (BEAM-13923) Java katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-13923: - Assignee: Israel Herraiz > Java katas answer placeholders with wrong locations > --- > > Key: BEAM-13923 > URL: https://issues.apache.org/jira/browse/BEAM-13923 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > > The answers of the Java katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (BEAM-13836) Python katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-13836: -- Fix Version/s: 2.37.0 Resolution: Fixed Status: Resolved (was: Open) > Python katas answer placeholders with wrong locations > - > > Key: BEAM-13836 > URL: https://issues.apache.org/jira/browse/BEAM-13836 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.37.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The answers of the Python katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of PyCharm. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (BEAM-13923) Java katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492433#comment-17492433 ] Israel Herraiz commented on BEAM-13923: --- Pull request submitted, awaiting review. > Java katas answer placeholders with wrong locations > --- > > Key: BEAM-13923 > URL: https://issues.apache.org/jira/browse/BEAM-13923 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Time Spent: 20m > Remaining Estimate: 0h > > The answers of the Java katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (BEAM-13923) Java katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-13923: -- Status: Open (was: Triage Needed) > Java katas answer placeholders with wrong locations > --- > > Key: BEAM-13923 > URL: https://issues.apache.org/jira/browse/BEAM-13923 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Time Spent: 20m > Remaining Estimate: 0h > > The answers of the Java katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (BEAM-10905) BigQueryIO withTempDataset assumes that it is running on Dataflow
[
https://issues.apache.org/jira/browse/BEAM-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478379#comment-17478379
]
Israel Herraiz commented on BEAM-10905:
---
This was a "self bug" that I logged so I would not forget (and I
forgot about the JIRA issue... ). I added the `withTempDataset`
option to BigQueryIO (as part of a customer requirement that needed to control
where the temporary data was being written to).
Using the project option in the pipeline options would work, but I added this
because I think that having the temp dataset in a different project could also
be useful for some customers.
I think I will now take the time to make the change :), and I will
add[~chamikara] as reviewer to the PR.
> BigQueryIO withTempDataset assumes that it is running on Dataflow
> -
>
> Key: BEAM-10905
> URL: https://issues.apache.org/jira/browse/BEAM-10905
> Project: Beam
> Issue Type: New Feature
> Components: extensions-java-gcp
>Affects Versions: 2.23.0
>Reporter: Israel Herraiz
>Priority: P2
> Labels: Clarified, bigquery
>
> The option {{withTempDataset}} of BigQueryIO only asks for a dataset name,
> assumes that the pipeline is running on Dataflow in a GCP project and uses
> that project to create the temp dataset.
> This option should accept a fully qualified dataset (project + dataset)
> instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (BEAM-10905) BigQueryIO withTempDataset assumes that it is running on Dataflow
[
https://issues.apache.org/jira/browse/BEAM-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz reassigned BEAM-10905:
-
Assignee: Israel Herraiz
> BigQueryIO withTempDataset assumes that it is running on Dataflow
> -
>
> Key: BEAM-10905
> URL: https://issues.apache.org/jira/browse/BEAM-10905
> Project: Beam
> Issue Type: New Feature
> Components: extensions-java-gcp
>Affects Versions: 2.23.0
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: P2
> Labels: Clarified, bigquery
>
> The option {{withTempDataset}} of BigQueryIO only asks for a dataset name,
> assumes that the pipeline is running on Dataflow in a GCP project and uses
> that project to create the temp dataset.
> This option should accept a fully qualified dataset (project + dataset)
> instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (BEAM-12468) Enable BigQueryIO to receive a project argument so that jobs will run on that project
[ https://issues.apache.org/jira/browse/BEAM-12468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479144#comment-17479144 ] Israel Herraiz commented on BEAM-12468: --- I think this issue is already fixed: https://github.com/apache/beam/pull/14980 I am not sure in which release it was included though. > Enable BigQueryIO to receive a project argument so that jobs will run on that > project > - > > Key: BEAM-12468 > URL: https://issues.apache.org/jira/browse/BEAM-12468 > Project: Beam > Issue Type: Bug > Components: io-java-gcp >Reporter: Pablo Estrada >Priority: P3 > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (BEAM-10905) BigQueryIO withTempDataset assumes that it is running on Dataflow
[
https://issues.apache.org/jira/browse/BEAM-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479145#comment-17479145
]
Israel Herraiz commented on BEAM-10905:
---
This has been fixed by BEAM-12468 (additional option to set a BigQuery project,
different to the GCP project).
> BigQueryIO withTempDataset assumes that it is running on Dataflow
> -
>
> Key: BEAM-10905
> URL: https://issues.apache.org/jira/browse/BEAM-10905
> Project: Beam
> Issue Type: New Feature
> Components: extensions-java-gcp
>Affects Versions: 2.23.0
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: P2
> Labels: Clarified, bigquery
>
> The option {{withTempDataset}} of BigQueryIO only asks for a dataset name,
> assumes that the pipeline is running on Dataflow in a GCP project and uses
> that project to create the temp dataset.
> This option should accept a fully qualified dataset (project + dataset)
> instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (BEAM-10905) BigQueryIO withTempDataset assumes that it is running on Dataflow
[
https://issues.apache.org/jira/browse/BEAM-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-10905:
--
Resolution: Fixed
Status: Resolved (was: Open)
Fixed by BEAM-12468
> BigQueryIO withTempDataset assumes that it is running on Dataflow
> -
>
> Key: BEAM-10905
> URL: https://issues.apache.org/jira/browse/BEAM-10905
> Project: Beam
> Issue Type: New Feature
> Components: extensions-java-gcp
>Affects Versions: 2.23.0
>Reporter: Israel Herraiz
>Assignee: Israel Herraiz
>Priority: P2
> Labels: Clarified, bigquery
>
> The option {{withTempDataset}} of BigQueryIO only asks for a dataset name,
> assumes that the pipeline is running on Dataflow in a GCP project and uses
> that project to create the temp dataset.
> This option should accept a fully qualified dataset (project + dataset)
> instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (BEAM-10905) BigQueryIO withTempDataset assumes that it is running on Dataflow
Israel Herraiz created BEAM-10905:
-
Summary: BigQueryIO withTempDataset assumes that it is running on
Dataflow
Key: BEAM-10905
URL: https://issues.apache.org/jira/browse/BEAM-10905
Project: Beam
Issue Type: Bug
Components: extensions-java-gcp
Affects Versions: 2.23.0
Reporter: Israel Herraiz
The option {{withTempDataset}} of BigQueryIO only asks for a dataset name,
assumes that the pipeline is running on Dataflow in a GCP project and uses that
project to create the temp dataset.
This option should accept a fully qualified dataset (project + dataset) instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-9804) beam.io.BigQuerySource needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-9804:
-
Fix Version/s: 2.26.0
> beam.io.BigQuerySource needs permissions to create datasets to be able to run
> queries
> -
>
> Key: BEAM-9804
> URL: https://issues.apache.org/jira/browse/BEAM-9804
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
>Reporter: Jonathan Sulman
>Priority: P3
> Fix For: 2.26.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Based on BEAM-8458, which was closed with a Java fix in 2.20.0. However, the
> bug still exists in the python SDK.
> When using BigQuerySource with the query option, BigQueryReader creates a
> temporary dataset to store the results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigqueryDataSource should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-9804) beam.io.BigQuerySource needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-9804:
-
Status: Resolved (was: Triage Needed)
> beam.io.BigQuerySource needs permissions to create datasets to be able to run
> queries
> -
>
> Key: BEAM-9804
> URL: https://issues.apache.org/jira/browse/BEAM-9804
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
>Reporter: Jonathan Sulman
>Priority: P3
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Based on BEAM-8458, which was closed with a Java fix in 2.20.0. However, the
> bug still exists in the python SDK.
> When using BigQuerySource with the query option, BigQueryReader creates a
> temporary dataset to store the results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigqueryDataSource should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-9804) beam.io.BigQuerySource needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-9804:
-
Status: Resolved (was: Resolved)
> beam.io.BigQuerySource needs permissions to create datasets to be able to run
> queries
> -
>
> Key: BEAM-9804
> URL: https://issues.apache.org/jira/browse/BEAM-9804
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
>Reporter: Jonathan Sulman
>Priority: P3
> Fix For: 2.26.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Based on BEAM-8458, which was closed with a Java fix in 2.20.0. However, the
> bug still exists in the python SDK.
> When using BigQuerySource with the query option, BigQueryReader creates a
> temporary dataset to store the results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigqueryDataSource should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (BEAM-9804) beam.io.BigQuerySource needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz reassigned BEAM-9804:
Assignee: Israel Herraiz
> beam.io.BigQuerySource needs permissions to create datasets to be able to run
> queries
> -
>
> Key: BEAM-9804
> URL: https://issues.apache.org/jira/browse/BEAM-9804
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
>Reporter: Jonathan Sulman
>Assignee: Israel Herraiz
>Priority: P3
> Fix For: 2.26.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Based on BEAM-8458, which was closed with a Java fix in 2.20.0. However, the
> bug still exists in the python SDK.
> When using BigQuerySource with the query option, BigQueryReader creates a
> temporary dataset to store the results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigqueryDataSource should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (BEAM-9804) beam.io.BigQuerySource needs permissions to create datasets to be able to run queries
[
https://issues.apache.org/jira/browse/BEAM-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz reassigned BEAM-9804:
Assignee: (was: Israel Herraiz)
> beam.io.BigQuerySource needs permissions to create datasets to be able to run
> queries
> -
>
> Key: BEAM-9804
> URL: https://issues.apache.org/jira/browse/BEAM-9804
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
>Reporter: Jonathan Sulman
>Priority: P3
> Fix For: 2.26.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Based on BEAM-8458, which was closed with a Java fix in 2.20.0. However, the
> bug still exists in the python SDK.
> When using BigQuerySource with the query option, BigQueryReader creates a
> temporary dataset to store the results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigqueryDataSource should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413024#comment-17413024 ] Israel Herraiz commented on BEAM-7261: -- I am working in adding support for `BasicSessionCredentials`. WIP in this branch in my fork of the Beam repo: https://github.com/iht/beam/tree/basic_session_credentials > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Priority: P3 > Original Estimate: 24h > Remaining Estimate: 24h > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-7261: Assignee: Israel Herraiz > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Original Estimate: 24h > Remaining Estimate: 24h > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on BEAM-7261 started by Israel Herraiz. > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Original Estimate: 24h > Remaining Estimate: 24h > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413690#comment-17413690 ] Israel Herraiz commented on BEAM-7261: -- PR submitted. > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Original Estimate: 24h > Time Spent: 10m > Remaining Estimate: 23h 50m > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-7261: - Fix Version/s: 2.34.0 > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Fix For: 2.34.0 > > Original Estimate: 24h > Time Spent: 20m > Remaining Estimate: 23h 40m > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-7261: - Resolution: Fixed Status: Resolved (was: In Progress) > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Fix For: 2.33.0 > > Original Estimate: 24h > Time Spent: 20m > Remaining Estimate: 23h 40m > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-7261: - Fix Version/s: (was: 2.34.0) 2.33.0 > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Fix For: 2.33.0 > > Original Estimate: 24h > Time Spent: 20m > Remaining Estimate: 23h 40m > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-7261) Add support for BasicSessionCredentials for aws credentials.
[ https://issues.apache.org/jira/browse/BEAM-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-7261: - Fix Version/s: (was: 2.33.0) 2.34.0 > Add support for BasicSessionCredentials for aws credentials. > > > Key: BEAM-7261 > URL: https://issues.apache.org/jira/browse/BEAM-7261 > Project: Beam > Issue Type: Improvement > Components: io-java-aws >Reporter: David Brown >Assignee: Israel Herraiz >Priority: P3 > Fix For: 2.34.0 > > Original Estimate: 24h > Time Spent: 20m > Remaining Estimate: 23h 40m > > Currently AWS for beam only supports basic Aws Credentials with a Secret and > a Key. Need to support session tokens for s3 instances with tighter > credentials. Would involve adding BasicSessionCredentials to the AwsModule. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-14007: -- Fix Version/s: 2.39.0 Resolution: Fixed Status: Resolved (was: In Progress) > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.39.0 > > Attachments: Screen Shot 2022-04-21 at 3.15.14 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:42) > at > org.gradle.configuration.project.BuildScriptPr
[jira] [Work started] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on BEAM-14007 started by Israel Herraiz. - > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-04-21 at 3.15.14 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:42) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26) > at > org.gradle.configuration.project.ConfigureActionsPro
[jira] [Commented] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529901#comment-17529901 ] Israel Herraiz commented on BEAM-14007: --- I did not change anything in the Java version :). I think it was just the time it took to be available to all users. I will be closing now this ticket. Thanks for the heads up about the katas! > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-04-21 at 3.15.14 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.pro
[jira] [Assigned] (BEAM-14400) Unable to start/download stepik Java Kata
[ https://issues.apache.org/jira/browse/BEAM-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-14400: - Assignee: Israel Herraiz > Unable to start/download stepik Java Kata > - > > Key: BEAM-14400 > URL: https://issues.apache.org/jira/browse/BEAM-14400 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-05-03 at 8.39.15 AM.png > > > Unable to download/start Java Kata via Stepik. > > Let's get this fixed so that users can experience and learn from Java Katas. > Some suggestions for fixing ( what I think to be likely cause ) found in the > bottom of the conversation found: > https://issues.apache.org/jira/browse/BEAM-14007 > > Screen shot attached. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (BEAM-14400) Unable to start/download stepik Java Kata
[ https://issues.apache.org/jira/browse/BEAM-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536081#comment-17536081 ] Israel Herraiz commented on BEAM-14400: --- I have uploaded the Java katas again from the current version available in the repo. Please could you check if the problem still persists? Thanks in advance. > Unable to start/download stepik Java Kata > - > > Key: BEAM-14400 > URL: https://issues.apache.org/jira/browse/BEAM-14400 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-05-03 at 8.39.15 AM.png > > > Unable to download/start Java Kata via Stepik. > > Let's get this fixed so that users can experience and learn from Java Katas. > Some suggestions for fixing ( what I think to be likely cause ) found in the > bottom of the conversation found: > https://issues.apache.org/jira/browse/BEAM-14007 > > Screen shot attached. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (BEAM-14400) Unable to start/download stepik Java Kata
[ https://issues.apache.org/jira/browse/BEAM-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-14400: -- Status: Open (was: Triage Needed) > Unable to start/download stepik Java Kata > - > > Key: BEAM-14400 > URL: https://issues.apache.org/jira/browse/BEAM-14400 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-05-03 at 8.39.15 AM.png > > > Unable to download/start Java Kata via Stepik. > > Let's get this fixed so that users can experience and learn from Java Katas. > Some suggestions for fixing ( what I think to be likely cause ) found in the > bottom of the conversation found: > https://issues.apache.org/jira/browse/BEAM-14007 > > Screen shot attached. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (BEAM-14006) Publish updated version of Python Kata to Stepik
[ https://issues.apache.org/jira/browse/BEAM-14006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-14006: - Assignee: Israel Herraiz > Publish updated version of Python Kata to Stepik > > > Key: BEAM-14006 > URL: https://issues.apache.org/jira/browse/BEAM-14006 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > > [https://github.com/apache/beam/blob/master/learning/katas/python/requirements.txt] > The recent change to requirements.txt ( to version 2.36 ) addresses issues > that had existed when trying to otherwise run on an M1 Mac. This is not what > is currently pulled down from anyone loading the katas from IntelliJ. > To complete this ticket, please publish the updated version to stepik so > users potentially have less trouble getting started. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (BEAM-14006) Publish updated version of Python Kata to Stepik
[ https://issues.apache.org/jira/browse/BEAM-14006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536110#comment-17536110 ] Israel Herraiz commented on BEAM-14006: --- I updated the Python katas in Stepik to Beam 2.38. I have also updated the katas in the repo. I am not sure about how to enable auto-publishing with Stepik. It requires the Edutools Jetbrains plugin, which AFAIK cannot be triggered from a script/automatically, it requires manual intervention. > Publish updated version of Python Kata to Stepik > > > Key: BEAM-14006 > URL: https://issues.apache.org/jira/browse/BEAM-14006 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > > [https://github.com/apache/beam/blob/master/learning/katas/python/requirements.txt] > The recent change to requirements.txt ( to version 2.36 ) addresses issues > that had existed when trying to otherwise run on an M1 Mac. This is not what > is currently pulled down from anyone loading the katas from IntelliJ. > To complete this ticket, please publish the updated version to stepik so > users potentially have less trouble getting started. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (BEAM-14400) Unable to start/download stepik Java Kata
[ https://issues.apache.org/jira/browse/BEAM-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538078#comment-17538078 ] Israel Herraiz commented on BEAM-14400: --- I have checked with two different people, and both could download the Katas and check that version was 8. Please could you double check that you are not reusing any cached version of the katas and that you are actually downloading the latest version from Stepik? > Unable to start/download stepik Java Kata > - > > Key: BEAM-14400 > URL: https://issues.apache.org/jira/browse/BEAM-14400 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-05-03 at 8.39.15 AM.png > > > Unable to download/start Java Kata via Stepik. > > Let's get this fixed so that users can experience and learn from Java Katas. > Some suggestions for fixing ( what I think to be likely cause ) found in the > bottom of the conversation found: > https://issues.apache.org/jira/browse/BEAM-14007 > > Screen shot attached. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (BEAM-14006) Publish updated version of Python Kata to Stepik
[ https://issues.apache.org/jira/browse/BEAM-14006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538080#comment-17538080 ] Israel Herraiz commented on BEAM-14006: --- The Katas are now updated, so I am resolving this ticket. Please reopen (or report a new issue) if you find any problem with the Python katas. I will also publish a step by step guide for the Beam team for them to consider about how to integrate it with the release process. > Publish updated version of Python Kata to Stepik > > > Key: BEAM-14006 > URL: https://issues.apache.org/jira/browse/BEAM-14006 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Time Spent: 40m > Remaining Estimate: 0h > > [https://github.com/apache/beam/blob/master/learning/katas/python/requirements.txt] > The recent change to requirements.txt ( to version 2.36 ) addresses issues > that had existed when trying to otherwise run on an M1 Mac. This is not what > is currently pulled down from anyone loading the katas from IntelliJ. > To complete this ticket, please publish the updated version to stepik so > users potentially have less trouble getting started. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (BEAM-14006) Publish updated version of Python Kata to Stepik
[ https://issues.apache.org/jira/browse/BEAM-14006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-14006: -- Fix Version/s: 2.39.0 Resolution: Fixed Status: Resolved (was: In Progress) > Publish updated version of Python Kata to Stepik > > > Key: BEAM-14006 > URL: https://issues.apache.org/jira/browse/BEAM-14006 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.39.0 > > Time Spent: 40m > Remaining Estimate: 0h > > [https://github.com/apache/beam/blob/master/learning/katas/python/requirements.txt] > The recent change to requirements.txt ( to version 2.36 ) addresses issues > that had existed when trying to otherwise run on an M1 Mac. This is not what > is currently pulled down from anyone loading the katas from IntelliJ. > To complete this ticket, please publish the updated version to stepik so > users potentially have less trouble getting started. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (BEAM-14006) Publish updated version of Python Kata to Stepik
[ https://issues.apache.org/jira/browse/BEAM-14006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on BEAM-14006 started by Israel Herraiz. - > Publish updated version of Python Kata to Stepik > > > Key: BEAM-14006 > URL: https://issues.apache.org/jira/browse/BEAM-14006 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Time Spent: 40m > Remaining Estimate: 0h > > [https://github.com/apache/beam/blob/master/learning/katas/python/requirements.txt] > The recent change to requirements.txt ( to version 2.36 ) addresses issues > that had existed when trying to otherwise run on an M1 Mac. This is not what > is currently pulled down from anyone loading the katas from IntelliJ. > To complete this ticket, please publish the updated version to stepik so > users potentially have less trouble getting started. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work started] (BEAM-14400) Unable to start/download stepik Java Kata
[ https://issues.apache.org/jira/browse/BEAM-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on BEAM-14400 started by Israel Herraiz. - > Unable to start/download stepik Java Kata > - > > Key: BEAM-14400 > URL: https://issues.apache.org/jira/browse/BEAM-14400 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > Attachments: Screen Shot 2022-05-03 at 8.39.15 AM.png > > > Unable to download/start Java Kata via Stepik. > > Let's get this fixed so that users can experience and learn from Java Katas. > Some suggestions for fixing ( what I think to be likely cause ) found in the > bottom of the conversation found: > https://issues.apache.org/jira/browse/BEAM-14007 > > Screen shot attached. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (BEAM-13923) Java katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-13923: - Assignee: Israel Herraiz > Java katas answer placeholders with wrong locations > --- > > Key: BEAM-13923 > URL: https://issues.apache.org/jira/browse/BEAM-13923 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Time Spent: 40m > Remaining Estimate: 0h > > The answers of the Java katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (BEAM-13923) Java katas answer placeholders with wrong locations
[ https://issues.apache.org/jira/browse/BEAM-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz updated BEAM-13923: -- Fix Version/s: 2.37.0 Resolution: Fixed Status: Resolved (was: Open) > Java katas answer placeholders with wrong locations > --- > > Key: BEAM-13923 > URL: https://issues.apache.org/jira/browse/BEAM-13923 > Project: Beam > Issue Type: Bug > Components: katas >Reporter: Israel Herraiz >Assignee: Israel Herraiz >Priority: P2 > Fix For: 2.37.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The answers of the Java katas are misplace because of the changes (tagging > text) added with BEAM-13395. The katas don't work well now with the Edu > plugin of IntelliJ. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Israel Herraiz reassigned BEAM-14007: - Assignee: Israel Herraiz > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:42) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26) > at > org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:35) > at > org.gradle.configuration.pr
[jira] [Commented] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523446#comment-17523446 ] Israel Herraiz commented on BEAM-14007: --- Can you try importing the katas from the latest version available at Github? https://github.com/apache/beam/tree/master/learning/katas/java I have not uploaded that yet to Stepik. So you are using a version that was released before M1 Macs even existed :). Please report back whether it works or not. > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.project.Buil
[jira] [Commented] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525449#comment-17525449 ] Israel Herraiz commented on BEAM-14007: --- Sorry, I meant importing that project in IntelliJ, as a local Edutools course. I see you checked that the code is ok. I will update the katas in Stepik asap. Thanks! > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:42) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScr
[jira] [Commented] (BEAM-14007) Java Kata -- Gradle Error? ( on M1 Mac )
[ https://issues.apache.org/jira/browse/BEAM-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525752#comment-17525752 ] Israel Herraiz commented on BEAM-14007: --- I have updated the Java katas in Stepik, to Beam 2.38. > Java Kata -- Gradle Error? ( on M1 Mac ) > -- > > Key: BEAM-14007 > URL: https://issues.apache.org/jira/browse/BEAM-14007 > Project: Beam > Issue Type: Improvement > Components: katas >Reporter: Bruce Arctor >Assignee: Israel Herraiz >Priority: P2 > > After following instructions found: > [https://beam.apache.org/blog/beam-kata-release/] to run the Java Katas, > received the following build error. Not sure what to make of the error, > might take some time later to further diagnose, but for now just reporting > the issue. > > Build file '//Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > > > > > == > > Build file '/Users/austin/Desktop/Beam Katas - Java/build.gradle' line: 56 > A problem occurred evaluating root project 'Beam_Kata'. > > Could not find method compile() for arguments > > [org.apache.beam:beam-sdks-java-core:2.19.0] on object of type > > org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. > * Try: > Run with --info or --debug option to get more log output. Run with --scan to > get full insights. > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'Beam_Kata'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) > at > org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75) > at > org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68) > at > org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74) > at > org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45) > at > org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74) > at > org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) > at > org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) > at > org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.lambda$applyToMutableState$0(DefaultProjectStateRegistry.java:280) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.fromMutableState(DefaultProjectStateRegistry.java:307) > at > org.gradle.api.internal.project.DefaultProjectStateRegistry$ProjectStateImpl.applyToMutableState(DefaultProjectStateRegistry.java:279) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:42) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26) > at > org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(Conf
