MySQL Bugs: #44350: load data infile "xyz.txt" into table xyz

Bug #44350	load data infile "xyz.txt" into table xyz
Submitted:	18 Apr 2009 6:39	Modified:	21 May 2009 20:38
Reporter:	Ron Nitzsche	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Parser	Severity:	S3 (Non-critical)
Version:	latest stable	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	LOAD DATA INFILE

Description:
Hi,

this is the table structur of xyz:

Field            | Type        | Null | Key | Default | Extra
-----------------+-------------+------+-----+---------+----------------
cust_id          | smallint(6) | NO   | PRI | NULL    | auto_increment
name             | char(25)    | NO   |     | NULL    |
forename         | char(25)    | YES  |     | NULL    |
street           | char(25)    | NO   |     | NULL    |
zip              | char(25)    | NO   |     | NULL    |
contactpartner   | char(25)    | YES  |     | NULL    |

If only a name is given(no forename, it's a firm and there's a contactpartner entry), if a name and forename is given it's a private person and we don't need a contactpartner.
So, i want to fill it via load data infile "xyz.txt" into table xyz; and if leaving the last entry of the last row blank (then, no entry for contactpartner is given, because it's a private person), it results in a warning

How to repeat:
to repeat, create the table how shown above and a textfile xyz.txt with the following entries:

1	Amazon		Road 5	11223	Mr.Amazon
2	Google		Trail 1	33441	Mrs.Google
3	Private Person	Street2	44433

Suggested fix:
none

Thank you for the bug report. Could you please read the below Manual section regarding the LOAD DATA INFILE Syntax pay attention about the FIELDS and LINES clauses if you don`t use them see the defaults used and if the source file was created accordingly. If you still have problems please specify the exactly server version (5.0.77..5.1.34) and attach here your xyz.txt. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".