Project Abstract
This project proposes implementing full text search of records and attributes in Tryton using Sphinx Search Sever ( http://sphinxsearch.com/ ) in a pythonic implementation. The idea is to improve Tryton search capability to a more flexible, scalable and powerful option.
I propose to use Sphinx Search Server because it is very fast (C++ language), can work in multiple OSes and has windows binaries (which might be included with NESO), it is very scalable, has proven success cases, we can implement in a pythonic way using SphinxAPI (which eliminates the need to install and support Apache Tomcat if we use Apache Solr), because it supports 2 of databases used by Tryton (PostgreSQL and Mysql), maybe can also support SQLlite3 through xmlpipe (if needed) and also supports NoSQL databases and future integrations (like MongoDB and CouchDB).
My commitment is to submit fully functional code, using a wiki or project management system to keep track of ideas and milestones (Google Code or Assembla), using mercurial as a repository, coding in a pythonic standard, following PEP008 Style Guide, make unit tests or doc tests, with a full set of English documentation generated using Sphinx Document Generator ( http://sphinx.pocoo.org/ ).
I propose to use Sphinx Search Server because it is very fast (C++ language), can work in multiple OSes and has windows binaries (which might be included with NESO), it is very scalable, has proven success cases, we can implement in a pythonic way using SphinxAPI (which eliminates the need to install and support Apache Tomcat if we use Apache Solr), because it supports 2 of databases used by Tryton (PostgreSQL and Mysql), maybe can also support SQLlite3 through xmlpipe (if needed) and also supports NoSQL databases and future integrations (like MongoDB and CouchDB).
My commitment is to submit fully functional code, using a wiki or project management system to keep track of ideas and milestones (Google Code or Assembla), using mercurial as a repository, coding in a pythonic standard, following PEP008 Style Guide, make unit tests or doc tests, with a full set of English documentation generated using Sphinx Document Generator ( http://sphinx.pocoo.org/ ).
As you gave that the idea is to improve Tryton search capability to a more flexible, scalable and powerful option so I personally feel that this is a great decision for this.
ReplyDeletesap project systems