Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6770A200CF3 for ; Wed, 13 Sep 2017 11:26:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 65DD01609CB; Wed, 13 Sep 2017 09:26:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ABA351609CA for ; Wed, 13 Sep 2017 11:26:03 +0200 (CEST) Received: (qmail 86058 invoked by uid 500); 13 Sep 2017 09:26:02 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 85944 invoked by uid 99); 13 Sep 2017 09:26:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2017 09:26:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B14A2C9823 for ; Wed, 13 Sep 2017 09:26:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -98.688 X-Spam-Level: X-Spam-Status: No, score=-98.688 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LTxenKn8PtH5 for ; Wed, 13 Sep 2017 09:26:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D4D9B61268 for ; Wed, 13 Sep 2017 09:26:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6F00CE010F for ; Wed, 13 Sep 2017 09:26:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2753C25382 for ; Wed, 13 Sep 2017 09:26:00 +0000 (UTC) Date: Wed, 13 Sep 2017 09:26:00 +0000 (UTC) From: "Tzu-Li (Gordon) Tai (JIRA)" To: dev@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FLINK-7614) Add a code snippet example of a valid POJO to "Data Types" documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 13 Sep 2017 09:26:04 -0000 Tzu-Li (Gordon) Tai created FLINK-7614: ------------------------------------------ Summary: Add a code snippet example of a valid POJO to "Data Types" documentation Key: FLINK-7614 URL: https://issues.apache.org/jira/browse/FLINK-7614 Project: Flink Issue Type: Improvement Components: Documentation Reporter: Tzu-Li (Gordon) Tai A user was struggling with working with POJO types, as reported in http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Exception-when-using-keyby-operator-td15435.html We seem to have similar "accidentally not valid POJO" problems every now and then from users. We can probably improve this by having a solid code snippet of a valid POJO under [1] that demonstrates the POJO rules, instead of just a text description of the rules. A guideline to check if your type is actually recognized as a POJO by Flink should also be included. [1] https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/types_serialization.html#rules-for-pojo-types -- This message was sent by Atlassian JIRA (v6.4.14#64029)