mapping of mysql:date/datetime/timestamp fields to es:date type

[JensLohr]

Hi, congratulations for the jdbc-river!

I've tested a case with different date formats, here is the MySQL dump:

CREATE TABLE IF NOT EXISTS `date_test` (
`id` int(10) NOT NULL AUTO_INCREMENT,
`field_int` int(10) NOT NULL,
`field_date` date NOT NULL,
`field_datetime` datetime NOT NULL,
`field_timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`field_datestring` char(10) COLLATE utf8_bin NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=3;

INSERT INTO `date_test` (`id`, `field_int`, `field_date`, `field_datetime`, `field_timestamp`, `field_datestring`) VALUES
(1, 1340223504, '2012-06-20', '2012-06-20 00:00:00', '2012-06-21 00:00:00', '2012-06-20'),
(2, 1123123123, '2012-06-16', '2012-06-20 22:54:11', '2012-06-21 00:02:31', '2012-06-16');

The resulting mapping in elasticsearch is:

mappings: {
jdbc: {
    properties: {
        id: {
            type: long
        }
        field_date: {
            type: long
        }
        field_timestamp: {
            type: long
        }
        field_datestring: {
            format: dateOptionalTime
            type: date
        }
        field_int: {
            type: long
        }
        field_datetime: {
            type: long
        }
    }
}
}

I did not expect that the field_datestring results in a date, but I guess this is being done by elasticsearch automatically.

Although field_int contains a timestamp, it is correct that it is being mapped to long.

For field_date, field_datetime, field_timestamp I would expect them to being mapped to a date/dateOptionalTime type.

Greetings from Munich,

Jens

[jprante]

Thanks for your report! The issue should be fixed with 1.1.0.