Unexpected behaviour when got error in the middle of mysqldump backup file import i am using mysql 5.5.40 version. i am importing a large .sql file having around 36000 lines using a script. The script contains below statements.

mysql -uxx -p &lt; dumpfile.sql 2 > error.log
cat error.log|mail -s "import error" a@something.com  

Sometime after executing the script, I got the mail saying "ERROR 1146 (42S02) at line 35687:Table 'dbname.tablename' doesn't exist. As i am not using force option while importing , it should not execute lines from 35688 to 36000 lines. it should abort when it hit with error. But when i have checked manually, it seems the lines are executed. Is it the expected behavior?

We know its expected behaviour when using source command in mysql command line client.
The behaviour is correct and it is incorrectly observed as per update from the questioner.
This got verified by further debugging the dumpload adding a debugging select syntax after the erroneous SQL in the dump.