[MCOL-3562] colxml parameter question Created: 2019-10-16  Updated: 2020-08-25  Resolved: 2019-10-16

Status: Closed
Project: MariaDB ColumnStore
Component/s: Documentation
Affects Version/s: 1.2.5
Fix Version/s: Icebox

Type: Bug Priority: Minor
Reporter: David Hill (Inactive) Assignee: David Hall (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

Asked by customer - Questions is is there an option -f for Colxml or is it just shown in the output run the colxml as shown in the Document example. And is the output correct based on what the custome is reporting.

/usr/local/mariadb/columnstore/bin/colxml tpch2 -j500
Running colxml with the following parameters:
2015-10-07 15:14:20 (9481) INFO :
Schema: tpch2
Tables:
Load Files:
-b 0
-c 1048576
-d |
-e 10
f CSV <------ here

From customer:

On this page
https://mariadb.com/kb/en/library/columnstore-bulk-data-loading/
In the section 'colxml syntax' there is no mention of the -f option.
When i do colxml -h on my system there is no mention of a -f option.
On the referenced page in the next section there is an example that contains '-f CSV'
yet the delimiter is shown as a pipe and the file extension as tbl

./colxml -h
Usage: colxml [options] dbName

Options:
-d Delimiter (default '|')
-e Maximum allowable errors (per table)
-h Print this message
-j Job id (numeric)
-l Load file name
-n "name in quotes"
-p Path for XML job description file that is generated
-s "Description in quotes"
-t Table name
-u User
-r Number of read buffers
-c Application read buffer size (in bytes)
-w I/O library buffer size (in bytes), used to read files
-x Extension of file name (default ".tbl")
-E EnclosedByChar (if data has enclosed values)
-C EscapeChar
-b Debug level (1-3)

dbName - Required parm specifying the name of the database;
all others are optional

Example:
colxml -t lineitem -j 123 tpch



 Comments   
Comment by David Hall (Inactive) [ 2019-10-16 ]

-f is deprecated and does nothing. It shouldn't show on the output.

Comment by David Hall (Inactive) [ 2019-10-16 ]

The document has been corrected

Comment by David Hill (Inactive) [ 2019-10-16 ]

thanks. So the KB document needs to be updated.

Generated at Thu Feb 08 02:43:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.