miyakawataku/pig

pig's Issues

No assignment for LOAD operator in a example of a tuple constructor

LOAD 'data' as (f1:int, f2:tuple(t1:int,t2:int,t3:int));

It should be

A = LOAD 'data' as (f1:int, f2:tuple(t1:int,t2:int,t3:int));

Typo: The exact signature of the function should clear from ... - > should be clear from ...

in udf.xml

MAX/MIN takes a bag as an argument

basic.html#sample says that SAMPLE partitions a relation (incorrect)

basic.html#sample says that

Partitions a relation into two or more relations.

Of course it is incorrect.

Typo: The STORE function specifies that the files -> The STORE statement specifies that the files

at func.xml

Use links to docs.oracle.com instead of java.sun.com

in basic.xml

The asterisk (*) projects fields, instead of tuples.

basic.html#projection says "In this example the asterisk (*) is used to project all tuples from relation A".

Typo: limit -> Limit in the "Term" subsection of "STRSPLIT"

in func.xml

Typo: three languages: Java, Python, JavaScript and Ruby

in udf.xml

basic.html#types-table-negative is not nested under #sign

basic.html#types-table-negative should be nested under #sign.

But not.

Typo: COUNT_STAR is used the count -> COUNT_STAR is used to count

Typo: COUNT_STAR is used the count -> COUNT_STAR is used to count

There is no individual section for the example of DEFINE and UDFs

On basic.html#define-udfs

Typo: JsonStorage -> JsonStorer

At func.xml

PigToStream and StreamToPig are badly indented

On basic.html#define-udfs.

Typo: reading delimiter -> using delimiter

At func.xml

"Syntax" subsection of LAST_INDEX_OF is wrong

LAST_INDEX_OF(expression) -> LAST_INDEX_OF(string, 'character', startIndex)

in func.xml

Colons leading "tuple", "bag", "map" cannot be omitted

basic.xml defines the syntax of tuple schemas:

alias[:tuple] (alias[:type]) [, (alias[:type]) …] )

Syntax of bag schemas:

alias[:bag] {tuple}

Syntax of map schemas:

alias<:map> [ <type> ]

Colons ( : ) leading "tuple", "bag", "map" are described as optional, but actually they are not.

A result of COGROUP for two relations has three fields, not two

In basic.html#GROUP

It's wrong.

The DESCRIBE operator shows the schema for relation X, which has two fields, "group" and "A" 

That should be

The DESCRIBE operator shows the schema for relation X, which has two fields, "group",  "A" , and "B"

Lack of description about ROUND(x)

in func.xml

Multiple fields are not enclosed in parentheses

basic.xml says "Multiple fields are enclosed in parentheses and separated by commas" but actually fields are not enclosed in parentheses.

Lack of description about REGEX_EXTRACT_ALL

When a whole regex pattern matches but a specific group does not match, what value is contained int the corresponding fields of the result tuple?

Star expressions represent tuples?

basic.xml says "the simplest tuple expression is the star expression, which represents all fields."

Is it correct? I think a star expression "" represents all fields, and "()" represents a tuple which contains all fields.

The Japanese version now translates the phrase literally.

Description of DIFF function is not precise

The description says:

Compares two fields in a tuple.

Actually, the function compares two bag arguments and returns a bag of tuples which are included in only one argument.

References without links on the section of LOAD operator

On basic.html#load.

This text has no link.

Schemas for Complex Data Types and Schemas for Multiple Types.

An alias for the streaming program is enclosed by quotation marks

On basic.html#ship-about

When two bytearrays are used ... with built in aggregate functions (such as SUM)

Strange.

in basic.xml

Typo in basic.xml: relationship -> relation

basic.xml says "If the schema of a relationship can't be inferred", but it should be "If the schema of a relation can't be inferred".

A map key must be a chararray, not only a scalar

basic.xml says "A map key must be a scalar", but actually a map key must be a chararray.

Typo: delimiters -> deliminters

Typo: delimiters -> deliminters

in func.xml

Typo: ROUND(x) -> CEIL(x)

in the heading of the result table of ROUND function.
in func.xml

If the relation contains more than one tuple, however, a runtime error is generated

in basic.xml

What occurs for no tuples?

basic.html refers to INNER COGROUP, which is already deprecated

In this example tuples are co-grouped and the INNER keyword is used asymmetrically on only one of the relations...

Wrong example: HDFS jar file -> HDFS pig file

On basic.html#register

basic.html says "Performs an outer join of two or more relations" (incorect)

Outer joins only works for two relations.

Star expressions represent tuples?

Wrong description about "limit" parameter of STRSPLIT

in func.xml

Typo: REGEX_EXTRACT -> REGEX_EXTRACT_ALL

In "Syntax" subsection of REGEX_EXTRACT_ALL in func.xml

Typo on basic.html#mapreduce: mr.jar -> mr1.jar

T/O

IntMax example lacks 'max' method

IntMax example lacks 'max' method, in udf.xml.

That method is called, but not defined.

The argument of MAX is a bag, not an int/long/double...

basic.html says about the argument of MAX:

An expression with data types int, long, float, double, or chararray.

But actually, MAX takes a bag of int/long/.....

Inaccurate description about nulls and group/cogroup on the original basic.xml

basic.xml says

When using the GROUP (COGROUP) operator with multiple relations, records with a null group key are considered different and are grouped separately.

However, nulls in a single relation are grouped altogether.

Typo? in basic.xml: deterministic -> non-deterministic

basic.xml says "Having a deterministic schema is very powerful", but it may be "Having a non-deterministic schema is very powerful".

Sample program of TOP function does not work: COUNT(*) must be COUNT(A)

in func.xml

MAX/MIN/SUM does not work for a bag created by TOBAG

Typo: an explicit cast if used -> "is used"

in basic.xml

Typo: limit -> lmit, express -> expressed

In basic.html#LIMIT

In this example the lmit is express as a scalar.

should be

In this example the limit is expressed as a scalar.

Semicolon is not needed in the example of REPLACE function

in func.xml

Description of MAX/MIN lacks a link to GROUP

T/O

basic.html says "The JOIN operator always performs an inner join" (incorrect)

T/O

Typo: A[i] = = B[i], k1 = = k2, v1 = = v2

in basic.xml

-> A[i] == B[i]
-> k1 == k2
-> v1 == v2