[Neos] Content Repository Search without dependencies

[Jacob Floyd]

If you use more than one server, you'll probably switch to elastic search.
As I understand it, the goal of this is to provide some simple searching
capabilities within Neos for the smaller projects that don't need anything
fancy.

Also, Neos sees the database via Doctrine, so we'd be restricted to
whatever Doctrine can do with MySQL, Postgres, and other databases
available through Doctrine.

Just my thoughts,
Jacob Floyd


On Mon, Apr 21, 2014 at 7:35 AM, Dominique Feyer <dfeyer at ttree.ch> wrote:

> Why not a simple flat index in MySQL ? With a table like nodeIdentifier,
> propertyName, propertyValue (maybe multiple propertyValueString,
> propertyValueInterger, … to optimize index usage in MySQL) ?
>
> The problem with Sqllite, is the scalability, as soon as we need a
> multiple server, this solution will not be usable.
>
> We definitively need a solution, and as any TYPO3CR installation use MySQL
> or Postgres, why not using this technologies for the default search
> implementation ?
>
> How the PHPCR implement search fonctionnalities ?
>
> Bests
>
> --
> ttree sàrl
> Dominique Feyer
> Rue du Valentin 34 et demi
> CH - 1004 Lausanne
> +41 21  312 36 35
> dfeyer at ttree.ch
> ttree.ch - @ttreeagency - plan d’accès
>
> Le 21 avril 2014 à 08:20:04, Pankaj Lele (pankaj at lelesys.com) a écrit:
>
> Hi Christian,
>
> Search engine without any major dependencies is an awesome idea.
> Great!
>
> --
> Pankaj Lele
> CTO - Lelesys, India
> http://www.lelesys.com
> Twitter: @pankajlele
>
> > Hi all,
> >
> > after researching and trying lots of things I created a simple, plain
> > PHP search engine that uses sqlite as storage [1]. On top of that an
> > adaptor to index and search the content repository [2].
> >
> > First of all I would like interested people to try it and second I want
> > to start a dialogue about a generic search interface. I already created
> > some interface class in the package but this should obviously decided
> > upon and at some point move to TYPO3CR or a TYPO3CR.SearchCommons
> > package.
> >
> > Keep in mind that this is to be considered alpha. I did some tests but
> > API and implementation might still change. Also currently there is no
> > trigger included that would update the index on content changes.
> > Still I would be happy to get your feedback on it.
> >
> > Cheers,
> > Christian
> >
> > [1] https://github.com/kitsunet/Flowpack.SimpleSearch
> > [2]
> https://github.com/kitsunet/Flowpack.SimpleSearch.ContentRepositoryAdaptor
>
>
>
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
>