[ 
https://issues.apache.org/jira/browse/IMPALA-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738366#comment-17738366
 ] 

ASF subversion and git services commented on IMPALA-12238:
----------------------------------------------------------

Commit 679d58fa6d970065f6c656ffcfd504794c2be516 in impala's branch 
refs/heads/master from Daniel Becker
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=679d58fa6 ]

IMPALA-12238: RandomNestedDataGenerator should take a seed argument

RandomNestedDataGenerator can be used to produce parquet files with
random data from Avro schemas. This change makes it possible to provide
a seed value for the random generator so the generated files are
reproducible. The seed can be given as the last (optional) command line
argument. It is parsed as a Java 'long'.

Testing:
 - manually verified that when run with the same arguments (including
   the seed), the data generator produces the same results

Change-Id: Iee33604bbfe12895100afbd0f98ac302dee9a238
Reviewed-on: http://gerrit.cloudera.org:8080/20136
Reviewed-by: Csaba Ringhofer <[email protected]>
Tested-by: Daniel Becker <[email protected]>


> RandomNestedDataGenerator should take a seed argument
> -----------------------------------------------------
>
>                 Key: IMPALA-12238
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12238
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Infrastructure
>            Reporter: Daniel Becker
>            Assignee: Daniel Becker
>            Priority: Major
>
> RandomNestedDataGenerator can be used to produce parquet files with random 
> data from Avro schemas. It should be possible to provide a seed value for the 
> random generator to make the generated files are reproducible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to