Bug #31005 Falcon: setting falcon_serial_log_dir has no effect
Submitted: 13 Sep 2007 19:25 Modified: 3 Dec 2007 13:13
Reporter: Hakan Küçükyılmaz Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version:6.0.3-alpha-debug OS:Any
Assigned to: Christopher Powers CPU Architecture:Any

[13 Sep 2007 19:25] Hakan Küçükyılmaz
Description:
Setting falcon_serial_log_dir has no effect. The serial log is created in the data dir in any case.

How to repeat:
Set falcon_serial_log_dir in my.cnf:

falcon_serial_log_dir = /data/log/mysql51

[21:23] root@test>SHOW variables LIKE 'falcon_serial_log_dir';
+-----------------------+-------------------+
| Variable_name         | Value             |
+-----------------------+-------------------+
| falcon_serial_log_dir | /data/log/mysql51 |
+-----------------------+-------------------+
1 row in set (0.00 sec)

[21:23] root@test>CREATE TABLE t1 (a int) Engine Falcon;
Query OK, 0 rows affected (0.01 sec)

Exit the mysql client and look into falcon_serial_log_dir directory:
lu0011:/data/log/mysql51# ls -las
total 8
4 drwxr-xr-x 2 root root 4096 2007-09-13 21:19 .
4 drwxr-xr-x 3 root root 4096 2007-09-13 21:19 ..
[13 Sep 2007 22:14] Miguel Solorzano
Thank you for the bug report.
[21 Oct 2007 21:37] Christopher Powers
The falcon_serial_log_dir parameter has been implemented via WL#4709, "Falcon: Serial log location parameter".
[21 Oct 2007 21:38] Christopher Powers
The correct worklog is WL#4079.
[26 Nov 2007 18:05] Hakan Küçükyılmaz
Verified that setting falcon_serial_log_dir works now.
[3 Dec 2007 13:14] MC Brown
A note has been added to the 6.0.4 changelog: 

Using falcon_serial_log_dir to set the location of the Falcon serial log would have no effect.