Like with REPLACE_ME ?
On Tue, Jun 16, 2015 at 4:57 AM, Maximilian Michels wrote:
> We could replace the placeholder "error" with something more meaningful
> though...
>
> On Tue, Jun 16, 2015 at 1:27 PM, Márton Balassi
> wrote:
>
>> Ok, never mind. I got it: it is decided later dependent on the
Setting up the partitioning etc is done automatically by the optimizer.
What is missing is a hash-based aggregator operator, that the optimizer can
choose as an alternative strategy to sort-based aggregation.
A good first step would be to have a look at how the hash join works, in
order to get an
Hi!
I think we actually have two discussions here, both of them important:
--
1) Null values in the Programming Language APIs
--
Fields in composite types may simply be null po
I added a comment with suggestions how to proceed in the JIRA issue.
2015-06-17 22:41 GMT+02:00 :
>
> Hello dear Developer,
> Currently aggregation functions are implemented based on sorting. We would
> like to add hash based aggregation to Flink. We would be thankful if you
> could tell as how t
Hello dear Developer,
Currently aggregation functions are implemented based on sorting. We
would like to add hash based aggregation to Flink. We would be
thankful if you could tell as how to get started (shall we add it as
an operator, runtime or ...). Our current thinking is to first hash
Rafiullah Momand created FLINK-2237:
---
Summary: Add hash-based Aggregation
Key: FLINK-2237
URL: https://issues.apache.org/jira/browse/FLINK-2237
Project: Flink
Issue Type: New Feature
Aljoscha Krettek created FLINK-2236:
---
Summary: RowSerializer and CaseClassComparator are not in sync
regarding Null-Values
Key: FLINK-2236
URL: https://issues.apache.org/jira/browse/FLINK-2236
Proje
On 17 Jun 2015, at 18:05, Aljoscha Krettek wrote:
> -1
>
> There is a bug in the newly introduced Null-Value support in RowSerializer:
> The serializer was changed to write booleans that signify if a field is
> null. For comparison this still uses the TupleComparatorBase (via
> CaseClassCompara
-1
There is a bug in the newly introduced Null-Value support in RowSerializer:
The serializer was changed to write booleans that signify if a field is
null. For comparison this still uses the TupleComparatorBase (via
CaseClassComparator) which is not aware of these changes.
The reason why no Unit
+1
Verified checksums and signatures
Built from source
Run bundled batch examples on a local setup
Run streaming example with checkpointed operator state on cluster, killed
taskmanagers underneath
On Wed, Jun 17, 2015 at 2:35 AM, Maximilian Michels wrote:
> Dear community!
>
> After careful tes
Maximilian Michels created FLINK-2235:
-
Summary: Local Flink cluster allocates too much memory
Key: FLINK-2235
URL: https://issues.apache.org/jira/browse/FLINK-2235
Project: Flink
Issue T
11 matches
Mail list logo