You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alternatively to the mapping file, we could keep the mapping definition inside the model.
I'd suggest a syntax like this:
public function elasticMapping()
{
return array(
'id' => array('type' => 'integer'),
'name' => array('type' => 'string', 'index'=>'not_analyzed'),
...
);
}
Then ./yiic elastic map --model=<model> would use the data above to find the right mapping.
Not sure, if we should also automate this for the regular auto-indexing on save(). This would require a check on every save operation, whether the mapping exists. Probably a bit too extreme.
The text was updated successfully, but these errors were encountered:
Alternatively to the mapping file, we could keep the mapping definition inside the model.
I'd suggest a syntax like this:
Then
./yiic elastic map --model=<model>
would use the data above to find the right mapping.Not sure, if we should also automate this for the regular auto-indexing on
save()
. This would require a check on every save operation, whether the mapping exists. Probably a bit too extreme.The text was updated successfully, but these errors were encountered: