masumsoft
commented
6 years ago @measwel for me the index is actually created and I didn't face any errors while searching, though the location type went into the index as a nested object instead of a geo_point type. May be you are accessing the model instances before they the getting initialized. I'm sharing my code here. Though i'm using Async suffixed promise based functions here, the callback based methods also does work. But the geo_point type defined in the properties is not having any effect on the elassandra index. Looks like it's an elassandra issue as the index properties is transferred to elassandra as is from express-cassandra.
index.js
var models = require('express-cassandra');
//Tell express-cassandra to use the models-directory, and
//use bind() to load the models using cassandra configurations.
models.setDirectory( __dirname + '/models').bind(
{
clientOptions: {
contactPoints: ['127.0.0.1'],
protocolOptions: { port: 9042 },
keyspace: 'mykeyspace',
queryOptions: {consistency: models.consistencies.one},
elasticsearch: {
host: 'http://localhost:9200',
apiVersion: '5.5',
requestTimeout: 1000 * 60 * 60,
sniffOnStart: true,
}
},
ormOptions: {
defaultReplicationStrategy : {
class: 'NetworkTopologyStrategy',
dc1: 1
},
migration: 'alter',
manageESIndex: true,
udts: {
geo_point: {
'lat': 'float',
'lon': 'float'
},
}
}
},
function(err) {
if(err) throw err;
console.log('model sync done!');
var Person = models.instance['Person'];
var person = new Person({
useruuid: models.uuid(),
name: 'Masum',
age: 32,
location: {
lat: 23.233441,
lon: -90.244535
},
created: { $db_function: 'toTimestamp(now())' }
});
person.saveAsync()
.then(() => {
return Person.searchAsync({q: 'name: Masum'});
})
.then((response) => {
console.log(response.hits.hits);
models.close();
})
.catch((err) => {
console.log(err);
models.close();
});
}
);models/PersonModel.js
module.exports = {
fields:{
useruuid: 'uuid',
name : 'text',
age : 'int',
location: {
type: 'frozen',
typeDef: '<geo_point>'
},
created : 'timestamp'
},
key:['name', 'created'],
clustering_order: { created: 'desc' },
es_index_mapping: {
discover: '.*',
properties: {
name: {
"type": "text",
"index": true
},
location: {
"type": "geo_point"
}
}
}
}
measwel
Extarys
In the docs for elassandra, the following is mentioned for mapping a geo_point:
Elasticearch Types | CQL Types | Comment geo_point | UDT geo_point or text | Built-In User Defined Type (1)
The references (1) and (2) in the documentation seem to be reversed. See: http://elassandra.readthedocs.io/en/latest/mapping.html?highlight=geo_point
For the time being, I have implemented the following:
And in my model I have:
The index is created, but the mapping is not right. The description field in the index is mapped to a keyword instead of analyzed text. The location field is also not mapped to a geo_point like specified.
UPDATE:
It seems that the mapping is created correctly, if I omit the fields in the cassandra table and only specify them in the es index properties object. These fields then also get created in the cassandra table. This is confusing, as the documentation states:
This suggests, that you can have fields specified for the cassandra table AND overwrite them in the properties specification. But in my case, the mapping only works when I specify the fields only in the properties for elastic search.