barryhunter
barryhunter
Ah yes, for backup at least a auto-flush would make sense. guess should flush `ATTRIBUTES` as well as `RTINDEX`. Guess, there may be a case for being able to lock...
That's good for listing the actual indexes. I think the point made in the other thread, is to use this .files table, to get the 'path' to the index files...
@[KarelWintersky](https://github.com/KarelWintersky) that is really a discussion for the original ticket about the backup script. https://github.com/manticoresoftware/manticoresearch/issues/821 ... this one, was just about the somewhat hidden function of getting a list of...
I have to wonder if 10B for max_matches, is simply way too big, such that it being ignored. (or worse integer overflowing/wrapping!) *(setting max_matches, could result in searchd trying allocate...
> select now() - d diff from t where diff < 0 Note that while that works, find it a bit slower, as it has to compute the virtual attribute...
Not really, because if know the name if the field can just use the .._len attribute directly. ie use `name_of_the_field_len` attribute. The sum(...) expression in the ranking expression is run...
You can invert the directionality of numeric attributes pretty easily concat(to_string(10000-i),... Actully staying as a numeric value may be worthwhile as manticore is not doing 'natural sorting' so numbers would...
Well in theory you CAN do it now. It's just that it may be a big resultset... SELECT id FROM index WHERE ... LIMIT 60000000 OPTION max_matches=60000000, ranker = none;...
I don't remember the exact details now, But pretty sure have had success using 'ATTACH' to move data from one RT index to the other. Each 'shard' an RT index...
Are you loading the version from gokml.net or a local copy? Google have recently changed policies, that the API can't be loaded without a key. I've put a key on...