[16.0][ADD] Connector typesense#168
Conversation
0d1c09b to
315789c
Compare
2bb016c to
aad62fa
Compare
|
@sebastienbeau @simahawk @lmignon i would be happy to here some feedback from you. |
lmignon
left a comment
There was a problem hiding this comment.
Thank you @MrTango for this contribution. I'd like to propose a first series of comments, but this seems to be going in the right direction. Great to have a new implementation for this new search engine which looks very interesting.
|
|
||
| setuptools.setup( | ||
| setup_requires=['setuptools-odoo'], | ||
| setup_requires=["setuptools-odoo"], |
There was a problem hiding this comment.
This file should not be modified.
|
|
||
| setuptools.setup( | ||
| setup_requires=['setuptools-odoo'], | ||
| setup_requires=["setuptools-odoo"], |
There was a problem hiding this comment.
This file should not be modified.
|
|
||
| setuptools.setup( | ||
| setup_requires=['setuptools-odoo'], | ||
| setup_requires=["setuptools-odoo"], |
There was a problem hiding this comment.
This file should not be modified.
|
|
||
| setuptools.setup( | ||
| setup_requires=['setuptools-odoo'], | ||
| setup_requires=["setuptools-odoo"], |
There was a problem hiding this comment.
This file should not be modified.
There was a problem hiding this comment.
I'm pretty sure this came from the pre-commit command, is there something wrong in the config than?
There was a problem hiding this comment.
@lmignon did i run the pre-commit command in a wrong way or how can i run just on the module I'm working on?
There was a problem hiding this comment.
@MrTango If it's changed by pre-commit you can ignore my comments
|
|
||
| setuptools.setup( | ||
| setup_requires=['setuptools-odoo'], | ||
| setup_requires=["setuptools-odoo"], |
There was a problem hiding this comment.
This file should not be modified.
|
thx @lmignon for your commends, I'll have a look at them. I would like to export more details of a product. |
The transformation to json is the responsibility of the serializer configured on your index. You can register your specific serializer. For example into the shoinvader project the |
|
thx for the tips, i found now also that it is using ir.export model and i can define the fields for the model there. |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
|
Sorry for the delay, i'll continue to work on this next month. |
970c156 to
4ceaebd
Compare
| print(">>> run _jobify_batch_recompute") | ||
| # breakpoint() |
There was a problem hiding this comment.
print and debug statements must be removed
| api_key_id = fields.Char( | ||
| help="Typesense Api Key ID", | ||
| string="Api Key ID", | ||
| groups="connector_search_engine.group_connector_search_engine_manager", | ||
| ) | ||
| api_key = fields.Char( | ||
| help="Typesense Api Key", | ||
| groups="connector_search_engine.group_connector_search_engine_manager", | ||
| ) |
There was a problem hiding this comment.
I would prefer to have these fields prefixed with TS
| def _get_adapter_class(self): | ||
| if self.backend_type == "typesense": | ||
| return TypesenseAdapter | ||
| else: |
| @@ -0,0 +1,37 @@ | |||
| Changelog | |||
|
@kobros-tech A lot of comments are not addressed. I'll be happy to merge this new connector but the code should be finalized. Feel free to make a new PR based on this one to complete the work. |
thanks, I did yesterday and I am working on it. |
|
@kobros-tech good to see your interest. I was hoping to work on it on the sprint, which was planned beginning of the year, but that didn't happen. @sebastienbeau any plans for a new date on that? |
|
Replaced by : #210 |
This is now fully working implementation of the Typesense backend.
Typesence is a free API compatible alternative to Algolia and easier to use than Elastic Search or Solr.
@sebastienbeau this needs the other two (#166 #167) PR's merged.