godfrey he created FLINK-13185:
--
Summary: Bump Calcite dependency to 1.20.0 in sql parser & flink
planner
Key: FLINK-13185
URL: https://issues.apache.org/jira/browse/FLINK-13185
Project: Flink
Hello Flink experts,
I believe the question below has been already asked, but since I couldn't find
my answer from internet, I'd love to reach out the community for help.
We basically want to find out the best configurations for Flink that running on
Kubernetes to achieve the best
Xintong Song created FLINK-13184:
Summary: Support launching task executors with multi-thread on
YARN.
Key: FLINK-13184
URL: https://issues.apache.org/jira/browse/FLINK-13184
Project: Flink
hehuiyuan created FLINK-13183:
-
Summary: Add PrintTableSink for Table & SQL APi
Key: FLINK-13183
URL: https://issues.apache.org/jira/browse/FLINK-13183
Project: Flink
Issue Type: Wish
Lun Zhang created FLINK-13182:
-
Summary: fix spelling mistake in flink-table/flink-sql-client
Key: FLINK-13182
URL: https://issues.apache.org/jira/browse/FLINK-13182
Project: Flink
Issue Type:
hehuiyuan created FLINK-13181:
-
Summary: Add a constructor function to CsvTableSink
Key: FLINK-13181
URL: https://issues.apache.org/jira/browse/FLINK-13181
Project: Flink
Issue Type: Improvement
hehuiyuan created FLINK-13180:
-
Summary: Add a constructor function to CsvTableSink
Key: FLINK-13180
URL: https://issues.apache.org/jira/browse/FLINK-13180
Project: Flink
Issue Type: Improvement
Jiangjie Qin created FLINK-13179:
Summary: Add document on how to run examples.
Key: FLINK-13179
URL: https://issues.apache.org/jira/browse/FLINK-13179
Project: Flink
Issue Type: Improvement
Hi Kostas,
It makes a lot of sense to just have one underlying mechanism (snapshot) to
save the state of a Flink job. And we can use that mechanism in different
scenarios, including checkpoint and user-triggered savepoint.
To facilitate the discussion, maybe it is useful to clarify a few design
Thanks for all your efforts Chesnay, it indeed improves a lot for our
develop experience. BTW, do you know how to find the master branch
information which the CI runs with?
For example, like this one:
https://travis-ci.com/flink-ci/flink/jobs/214542568
It shows pass with the commits, which
Bowen Li created FLINK-13178:
Summary: persist Flink's functions to catalog
Key: FLINK-13178
URL: https://issues.apache.org/jira/browse/FLINK-13178
Project: Flink
Issue Type: Sub-task
Bowen Li created FLINK-13177:
Summary: make FunctionCatalog able to reference functions across
catalogs
Key: FLINK-13177
URL: https://issues.apache.org/jira/browse/FLINK-13177
Project: Flink
Thanks a lot guys for your quick response and fix.
I am running a local release on that tag now.
Best regards,
Bekir
> On 9 Jul 2019, at 21:19, jincheng sun wrote:
>
> Thanks Bekir Oguz and Chesnay!
>
> Sorry for that, I forgot push the tag, I've pushed the tag to the repo
> now.
Bowen Li created FLINK-13176:
Summary: remember current catalog and database in SQL CLI
SessionContext
Key: FLINK-13176
URL: https://issues.apache.org/jira/browse/FLINK-13176
Project: Flink
Bowen Li created FLINK-13175:
Summary: FLINK-12951 breaks SQL CLI's ExecutionContextTest
Key: FLINK-13175
URL: https://issues.apache.org/jira/browse/FLINK-13175
Project: Flink
Issue Type: Bug
Thanks Bekir Oguz and Chesnay!
Sorry for that, I forgot push the tag, I've pushed the tag to the repo
now. https://github.com/apache/flink/tree/release-1.8.1
Thanks again, and I'm very sorry for my negligence has caused confusion in
your use.
Thanks,
Jincheng
Bekir Oguz 于2019年7月10日周三
Yu Li created FLINK-13174:
-
Summary: Changes of HiveTableSinkTest in FLINK-13068 introduces
compilation error
Key: FLINK-13174
URL: https://issues.apache.org/jira/browse/FLINK-13174
Project: Flink
Hi,
I would like to build the 1.8.1 version of the flink-connector-kinesis module
but cannot find the release tag in GitHub repo.
I see release candidate 1 (release-1.8.1-rc1) tag, but not sure whether this
consists of all the 40 bug fixes in 1.8.1 or not.
Which hash or tag should I use to
Yes, it appears the 1.8.1 tag is missing. The 1.8.1-rc1 tag is an
equivalent that you can use for the time being.
Alternatively you could of course also use the source release to build
the connector.
@jincheng Could you add the proper 1.8.1 tag?
On 09/07/2019 16:38, Bekir Oguz wrote:
Hi,
I
Nico Kruber created FLINK-13173:
---
Summary: Only run openSSL tests if desired
Key: FLINK-13173
URL: https://issues.apache.org/jira/browse/FLINK-13173
Project: Flink
Issue Type: Sub-task
Nico Kruber created FLINK-13172:
---
Summary: JVM crash with dynamic netty-tcnative wrapper to openSSL
on some OS
Key: FLINK-13172
URL: https://issues.apache.org/jira/browse/FLINK-13172
Project: Flink
Gyula Fora created FLINK-13171:
--
Summary: Add withParameters(Configuration) method to DataStream
operators
Key: FLINK-13171
URL: https://issues.apache.org/jira/browse/FLINK-13171
Project: Flink
Hi,
I would like to build the 1.8.1 version of the flink-connector-kinesis module
but cannot find the release tag in GitHub repo.
I see release candidate 1 (release-1.8.1-rc1) tag, but not sure whether this
consists of all the 40 bug fixes in 1.8.1 or not.
Which hash or tag should I use to
Hi Aljoscha,
Thanks for the quick response. Yes, you are right. I meant "Voted and
accepted FLIPs should be immutable". Sorry for the confusion.
Thanks,
Jiangjie (Becket) Qin
On Tue, Jul 9, 2019 at 10:09 PM Aljoscha Krettek
wrote:
> +1 to what Becket said.
>
> I have one comment on 5.: I
Hi Gordon,
Will branch 1.9 be cut out today? We're really looking forward to the blink
features in 1.9.
Thanks,
Qi
On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai
wrote:
> Thanks for the updates so far everyone!
>
> Since support for the new Blink-based Table / SQL runner and fine-grained
+1 to what Becket said.
I have one comment on 5.: I think you meant that they should be immutable once
they have been voted on and accepted. During the initial proposal and
discussion they will change, of course. At least that’s what I think
Aljoscha
> On 9. Jul 2019, at 11:29, Becket Qin
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is huwh, my fullname is HuWeihua.
Thanks a lot.
Rui Li created FLINK-13170:
--
Summary: Planner should get table factory from catalog when
creating sink for CatalogTable
Key: FLINK-13170
URL: https://issues.apache.org/jira/browse/FLINK-13170
Project: Flink
Andrey Zagrebin created FLINK-13169:
---
Summary: IT test for fine-grained recovery (task executor failures)
Key: FLINK-13169
URL: https://issues.apache.org/jira/browse/FLINK-13169
Project: Flink
godfrey he created FLINK-13168:
--
Summary: clarify isBatch/isStreaming/isBounded flag in flink
planner and blink planner
Key: FLINK-13168
URL: https://issues.apache.org/jira/browse/FLINK-13168
Project:
Luo Gen created FLINK-13167:
---
Summary: Introduce FlinkML import/export framework
Key: FLINK-13167
URL: https://issues.apache.org/jira/browse/FLINK-13167
Project: Flink
Issue Type: Sub-task
This discussion thread has been quiet for some time. It looks most people
think sticking to a strict voting process is a good idea.
In addition to that, there are a few related details that are also
discussed, I listed them below and personally I am +1 on all of them.
1. Stick to the current
Till Rohrmann created FLINK-13166:
-
Summary: Support batch slot requests
Key: FLINK-13166
URL: https://issues.apache.org/jira/browse/FLINK-13166
Project: Flink
Issue Type: Sub-task
Till Rohrmann created FLINK-13165:
-
Summary: Complete requested slots in request order
Key: FLINK-13165
URL: https://issues.apache.org/jira/browse/FLINK-13165
Project: Flink
Issue Type:
Congxian Qiu(klion26) created FLINK-13164:
-
Summary: Add a putAndGet benchmark for StateBenchmark
Key: FLINK-13164
URL: https://issues.apache.org/jira/browse/FLINK-13164
Project: Flink
Jeff Zhang created FLINK-13163:
--
Summary: Default value of slot.request.timeout is too small for
batch job
Key: FLINK-13163
URL: https://issues.apache.org/jira/browse/FLINK-13163
Project: Flink
36 matches
Mail list logo
