[jira] [Created] (CALCITE-2781) Add Travis job to test against PostgreSQL

Vladimir Sitnikov created CALCITE-2781: -- Summary: Add Travis job to test against PostgreSQL Key: CALCITE-2781 URL: https://issues.apache.org/jira/browse/CALCITE-2781 Project: Calcite

[jira] [Created] (CALCITE-2780) Replace UnmodifiableArrayList with JDK Functions

BELUGA BEHR created CALCITE-2780: Summary: Replace UnmodifiableArrayList with JDK Functions Key: CALCITE-2780 URL: https://issues.apache.org/jira/browse/CALCITE-2780 Project: Calcite Issue

[jira] [Created] (CALCITE-2779) Remove References to StringBuffer

BELUGA BEHR created CALCITE-2779: Summary: Remove References to StringBuffer Key: CALCITE-2779 URL: https://issues.apache.org/jira/browse/CALCITE-2779 Project: Calcite Issue Type:

[jira] [Created] (CALCITE-2778) CompoundClosableAllocation Prefer ArrayList

BELUGA BEHR created CALCITE-2778: Summary: CompoundClosableAllocation Prefer ArrayList Key: CALCITE-2778 URL: https://issues.apache.org/jira/browse/CALCITE-2778 Project: Calcite Issue Type:

Re: "Patch" flag vs. "pull-request-available" label

+1 for standardizing. No opinion on which one we use. -- Michael Mior mm...@apache.org Le lun. 7 janv. 2019 à 16:13, Julian Hyde a écrit : > There seem to be two mechanisms to indicate that a pull-request is > available for a JIRA case. > > 1. The “Patch” flag (13 issues); see >

[jira] [Created] (CALCITE-2777) Inclusion of Period data type in calcite.

Garvit created CALCITE-2777: --- Summary: Inclusion of Period data type in calcite. Key: CALCITE-2777 URL: https://issues.apache.org/jira/browse/CALCITE-2777 Project: Calcite Issue Type: New Feature

[jira] [Created] (CALCITE-2776) Wrong value when accessing struct types with one attribute

Stamatis Zampetakis created CALCITE-2776: Summary: Wrong value when accessing struct types with one attribute Key: CALCITE-2776 URL: https://issues.apache.org/jira/browse/CALCITE-2776 Project: