[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=293975=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293975
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 13/Aug/19 15:52
Start Date: 13/Aug/19 15:52
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on pull request #9314:
[CHERRY-PICK][BEAM-7916] Add ElasticsearchIO query parameter to take a
ValueProvider (#9285)
URL: https://github.com/apache/beam/pull/9314
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 293975)
Time Spent: 3h (was: 2h 50m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Assignee: Alexey Romanenko
>Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=293729=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293729
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 13/Aug/19 08:42
Start Date: 13/Aug/19 08:42
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #9285: [BEAM-7916]
Add ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-520745131
Hi @oliverhenlich, yes, I reverted commit in `release-2.14.0` and created
new PR against master (I cherry-picked your commit, so your credits should be
kept). So, I think there is nothing to do for now from your side. This fix will
appear in `2.16` since `2.15` branch was already cut 2 weeks ago.
PS: Yes, you are right, it was not related to your changes, thanks to
@RyanSkraba to rerun and it's ok now.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 293729)
Time Spent: 2h 50m (was: 2h 40m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Assignee: Alexey Romanenko
>Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=293687=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293687
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 13/Aug/19 07:30
Start Date: 13/Aug/19 07:30
Worklog Time Spent: 10m
Work Description: RyanSkraba commented on issue #9314:
[CHERRY-PICK][BEAM-7916] Add ElasticsearchIO query parameter to take a
ValueProvider (#9285)
URL: https://github.com/apache/beam/pull/9314#issuecomment-520722956
Run Java PreCommit
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 293687)
Time Spent: 2h 40m (was: 2.5h)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Assignee: Alexey Romanenko
>Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=293442=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293442
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 12/Aug/19 22:26
Start Date: 12/Aug/19 22:26
Worklog Time Spent: 10m
Work Description: oliverhenlich commented on issue #9285: [BEAM-7916] Add
ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-520618091
Hi @aromanenko-dev, sorry for the delay! Just got back to this. It looks
like you've already taken care of this with PR:
https://github.com/apache/beam/pull/9305 and
https://github.com/apache/beam/pull/9314. Do I still need to do something?
What version would this fix then appear in 2.15?
PS: I noticed the last PR https://github.com/apache/beam/pull/9314 is
failing but I don't think it has anything to do with my change.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 293442)
Time Spent: 2.5h (was: 2h 20m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Assignee: Alexey Romanenko
>Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[ https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=293199=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293199 ] ASF GitHub Bot logged work on BEAM-7916: Author: ASF GitHub Bot Created on: 12/Aug/19 15:22 Start Date: 12/Aug/19 15:22 Worklog Time Spent: 10m Work Description: aromanenko-dev commented on pull request #9314: [CHERRY-PICK][BEAM-7916] Add ElasticsearchIO query parameter to take a ValueProvider (#9285) URL: https://github.com/apache/beam/pull/9314 Cherry-picked from `release-2.14.0`, where tt was merged by mistake. Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] [**Choose reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and mention them in a comment (`R: @username`). - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). Post-Commit Tests Status (on master branch) Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark --- | --- | --- | --- | --- | --- | --- | --- Go | [](https://builds.apache.org/job/beam_PostCommit_Go/lastCompletedBuild/) | --- | --- | [](https://builds.apache.org/job/beam_PostCommit_Go_VR_Flink/lastCompletedBuild/) | --- | --- | [](https://builds.apache.org/job/beam_PostCommit_Go_VR_Spark/lastCompletedBuild/) Java | [](https://builds.apache.org/job/beam_PostCommit_Java/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Spark_Batch/lastCompletedBuild/) Python | [](https://builds.apache.org/job/beam_PostCommit_Python2/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Python35/lastCompletedBuild/)[](https://builds.apache.org/job/beam_PostCommit_Python36/lastCompletedBuild/)[![Build
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=292092=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-292092
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 09/Aug/19 15:03
Start Date: 09/Aug/19 15:03
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #9285: [BEAM-7916]
Add ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-519855182
@oliverhenlich Yes, my bad, I didn't pay an attention that this PR was
against `release-2.14.0` branch instead of `master`. Thank you for pointing on
this.
I'll revert this commit (since release 2.14 is already done) and could you
create another PR against `master` branch?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 292092)
Time Spent: 2h 10m (was: 2h)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Assignee: Alexey Romanenko
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291988=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291988
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 09/Aug/19 10:32
Start Date: 09/Aug/19 10:32
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on pull request #9305: Revert
"[BEAM-7916] Add ElasticsearchIO query parameter to take a ValueProvider"
URL: https://github.com/apache/beam/pull/9305
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291988)
Time Spent: 2h (was: 1h 50m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Assignee: Alexey Romanenko
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291955=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291955
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 09/Aug/19 09:42
Start Date: 09/Aug/19 09:42
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #9285: [BEAM-7916]
Add ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-519855182
@oliverhenlich Yes, my bad, I didn't pay an attention that this PR was
against `release-2.14.0` branch instead of `master`. I'll revert this commit
(since release 2.14 is already done) and could you create another PR against
`master` branch?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291955)
Time Spent: 1h 50m (was: 1h 40m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.16.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291949=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291949
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 09/Aug/19 09:36
Start Date: 09/Aug/19 09:36
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on pull request #9305: Revert
"[BEAM-7916] Add ElasticsearchIO query parameter to take a ValueProvider"
URL: https://github.com/apache/beam/pull/9305
It was mistakenly merged into branch `release-2.14.0` instead of `master`
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291949)
Time Spent: 1h 40m (was: 1.5h)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.16.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291658=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291658
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 08/Aug/19 23:52
Start Date: 08/Aug/19 23:52
Worklog Time Spent: 10m
Work Description: oliverhenlich commented on issue #9285: [BEAM-7916] Add
ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-519727490
Hi @aromanenko-dev,
Thanks for merging this! I just realized that it's been merged into `2.14.0`
which has already been released. Will that make it into the next version? What
is the next version? On the Jira it says `2.16.0`.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291658)
Time Spent: 1.5h (was: 1h 20m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.16.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291216=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291216
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 08/Aug/19 12:09
Start Date: 08/Aug/19 12:09
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on pull request #9285:
[BEAM-7916] Add ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291216)
Time Spent: 1h 20m (was: 1h 10m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291215=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291215
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 08/Aug/19 12:08
Start Date: 08/Aug/19 12:08
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #9285: [BEAM-7916]
Add ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-519490884
R: @aromanenko-dev
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291215)
Time Spent: 1h 10m (was: 1h)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (BEAM-7916) Add ElasticsearchIO query parameter to take a ValueProvider
[
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291212=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291212
]
ASF GitHub Bot logged work on BEAM-7916:
Author: ASF GitHub Bot
Created on: 08/Aug/19 12:07
Start Date: 08/Aug/19 12:07
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #9285: [BEAM-7916]
Add ElasticsearchIO query parameter to take a ValueProvider
URL: https://github.com/apache/beam/pull/9285#issuecomment-519490884
R: @aromanenko-dev
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 291212)
Time Spent: 1h (was: 50m)
> Add ElasticsearchIO query parameter to take a ValueProvider
> ---
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
>Affects Versions: 2.14.0
>Reporter: Oliver Henlich
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The
> problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which
> means the query must be known when the pipleline/Google Dataflow Template is
> built.
> It would be great if we could change the parameter on the {{withQuery()}}
> method from {{String}} to {{ValueProvider}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
