Is this really a problem when you could easily enough create a TextField and call setTokenStream?
Does your remote client have Solr-core and all its dependencies on the classpath? That's one way to do it... and presumably the direction you are going because you're asking how to work with PreAnalyzedParser which is in solr-core. *Alternatively*, only bring in Lucene core and construct things yourself in the right format. You could copy PreAnalyzedParser into your codebase so that you don't have to reinvent any wheels, even though that's awkward. Perhaps that ought to be in Solrj? But no we don't want SolrJ depending on Lucene-core, though it'd make a fine "optional" dependency. On Wed, Apr 4, 2018 at 4:53 AM Markus Jelsma <markus.jel...@openindex.io> wrote: > Hello, > > We intend to move to PreAnalyzed URP for analysis offloading. Browsing the > Javadocs i came across the SchemaRequest API looking for a way to get a > Field object remotely, which i seem to need for > JsonPreAnalyzedParser.toFormattedString(Field f). But all i can get from > SchemaRequest API is FieldTypeRepresentation, which offers me > getIndexAnalyzer() but won't allow me to construct a Field object. > > So, to analyze remotely i do need an index-time analyzer. I can get it, > but not turn it into a Field object, which the PreAnalyzedParser for some > reason wants. > > Any hints here? I must be looking the wrong way. > > Many thanks! > Markus > -- Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
