Permission for a new contributor
Hi everyone, My name is Mingdao and I would like to work on FLINK-4582. My JIRA id is mingdaoy. Could someone grant me access to ticket assignment so I can start contributing? Thank you, Mingdao
Re: Permission for a new contributor
Hello Mingdao, you now have contributor permissions. On 15.08.2017 09:18, Mingdao wrote: Hi everyone, My name is Mingdao and I would like to work on FLINK-4582. My JIRA id is mingdaoy. Could someone grant me access to ticket assignment so I can start contributing? Thank you, Mingdao
Re: Permission for a new contributor
Thank you Chesnay ! -- View this message in context: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Permission-for-a-new-contributor-tp19250p19252.html Sent from the Apache Flink Mailing List archive. mailing list archive at Nabble.com.
[jira] [Created] (FLINK-7449) Improve and enhance documentation for incremental checkpoints
Stefan Richter created FLINK-7449: - Summary: Improve and enhance documentation for incremental checkpoints Key: FLINK-7449 URL: https://issues.apache.org/jira/browse/FLINK-7449 Project: Flink Issue Type: Improvement Components: Documentation Affects Versions: 1.4.0 Reporter: Stefan Richter Assignee: Stefan Richter Priority: Minor We should provide more details about incremental checkpoints in the documentation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7450) Bounded generic POJO field is identified as Object by TypeExtractor
Timo Walther created FLINK-7450:
---
Summary: Bounded generic POJO field is identified as Object by
TypeExtractor
Key: FLINK-7450
URL: https://issues.apache.org/jira/browse/FLINK-7450
Project: Flink
Issue Type: Bug
Components: Type Serialization System
Reporter: Timo Walther
The TypeExtractor does not correctly handle POJO fields with bounded generics.
For example:
{code}
public class Foo implements Serializable {
public SomeKey someKey;
public Foo() {}
public Foo(SomeKey someKey) {
this.someKey = someKey;
}
}
{code}
Is identified as:
{code}
PojoType]>
{code}
So even though the reflection field has a type, the type information only
describes a Object class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7451) Query fails when non-ascii characters are used in string literals
Jark Wu created FLINK-7451:
--
Summary: Query fails when non-ascii characters are used in string
literals
Key: FLINK-7451
URL: https://issues.apache.org/jira/browse/FLINK-7451
Project: Flink
Issue Type: Bug
Components: Table API & SQL
Reporter: Jark Wu
Assignee: Jark Wu
I found that using non-ascii characters in string literals causes calcite
planner to throw the following exception:
{code}
org.apache.calcite.runtime.CalciteException: Failed to encode '%测试%' in
character set 'ISO-8859-1'
{code}
The query is
{code}
SELECT * FROM T WHERE f0 LIKE '%测试%'
{code}
The reason for the issue is that calcite uses latin encoding ('ISO-8859-1') by
default. In order to pass non-latin characters we should use unicode encoding
as default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7452) Add helper methods for all built-in Flink types to Types
Timo Walther created FLINK-7452:
---
Summary: Add helper methods for all built-in Flink types to Types
Key: FLINK-7452
URL: https://issues.apache.org/jira/browse/FLINK-7452
Project: Flink
Issue Type: Improvement
Components: Type Serialization System
Reporter: Timo Walther
Assignee: Timo Walther
Sometimes it is very difficult to provide `TypeInformation` manually, in case
some extraction fails or is not available. {{TypeHint}}s should be the
preferred way but this methods can ensure correct types.
I propose to add all built-in Flink types to the {{Types}}. Such as:
{code}
Types.POJO(MyPojo.class)
Types.POJO(Map)
Types.GENERIC(Object.class)
Types.TUPLE(TypeInformation, ...)
Types.MAP(TypeInformation, TypeInformation)
{code}
The methods should validate that the returned type is exactly the requested
type. And especially in case of POJO should help creating {{PojoTypeInfo}}.
Once this is in place, we can deprecate the {{TypeInfoParser}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (FLINK-7453) FlinkKinesisProducer logs empty aws region
Bowen Li created FLINK-7453:
---
Summary: FlinkKinesisProducer logs empty aws region
Key: FLINK-7453
URL: https://issues.apache.org/jira/browse/FLINK-7453
Project: Flink
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Bowen Li
Assignee: Bowen Li
Priority: Minor
Fix For: 1.4.0, 1.3.3
I saw the following logs in my taskmanager.log
{code:java}
2017-08-16 04:28:58,068 INFO
org.apache.flink.streaming.connectors.kinesis.FlinkKinesisProducer - Started
Kinesis producer instance for region ''
2017-08-16 04:28:58,708 INFO
org.apache.flink.kinesis.shaded.com.amazonaws.services.kinesis.producer.KinesisProducer
- Extracting binaries to /tmp/amazon-kinesis-producer-native-binaries
2017-08-16 04:28:58,712 INFO
org.apache.flink.streaming.connectors.kinesis.FlinkKinesisProducer - Started
Kinesis producer instance for region ''
2017-08-16 04:28:59,305 INFO
org.apache.flink.kinesis.shaded.com.amazonaws.services.kinesis.producer.KinesisProducer
- Extracting binaries to /tmp/amazon-kinesis-producer-native-binaries
2017-08-16 04:28:59,309 INFO
org.apache.flink.streaming.connectors.kinesis.FlinkKinesisProducer - Started
Kinesis producer instance for region ''
2017-08-16 04:28:59,898 INFO
org.apache.flink.kinesis.shaded.com.amazonaws.services.kinesis.producer.KinesisProducer
- Extracting binaries to /tmp/amazon-kinesis-producer-native-binaries
{code}
I need to figure it out why first, and then propose a fix.
cc [~tzulitai]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
