Hello,
I would like to report / discuss a problem I am having with the replicator failing to parse the query. The query is failing to parse due to the value in a result containing the word "Select".
It appears that as these rows are being parsed there is a check for a nested select statement that would be contained within the value of a field and kick off a sub query. Perhaps this is related to the documentation on nested documents that may be coming in the future or perhaps I am not using this plugin correctly.
file: lib/fluent/plugin/in_mysql_replicator.rb
issue: row.select {|k, v| v.to_s.strip.match(/^SELECT/i) }.each do |k, v|
Is this condition and subsequent iteration needed if so, what is it used for I am not seeing it's purpose described.
I apologize in advance if this is a non issue. This plugin sounds promising for our needs as the jdbc river is lacking a solid delete process. I am hopeful that this is an issue on my end or that you know of a work around.
example mysql :
$ mysql -e "create database myweb"
$ mysql myweb -e "create table search_test(id int auto_increment, text text, test text, PRIMARY KEY (id))"
$ mysql myweb -e "insert into search_test(text, test) values('aaa', 'Select me and live forever')"
query select * from myweb;
mysql_replicator: failed to execute query.
error: Unknown column 'me' in 'field list'
Hello,
I would like to report / discuss a problem I am having with the replicator failing to parse the query. The query is failing to parse due to the value in a result containing the word "Select".
It appears that as these rows are being parsed there is a check for a nested select statement that would be contained within the value of a field and kick off a sub query. Perhaps this is related to the documentation on nested documents that may be coming in the future or perhaps I am not using this plugin correctly.
Is this condition and subsequent iteration needed if so, what is it used for I am not seeing it's purpose described.
I apologize in advance if this is a non issue. This plugin sounds promising for our needs as the jdbc river is lacking a solid delete process. I am hopeful that this is an issue on my end or that you know of a work around.
example mysql :