machinio / solrb Goto Github PK

View Code? Open in Web Editor NEW

39.0 7.0 1.0 301 KB

Solr + Ruby + OOP + ❤️ = Solrb

License: MIT License

Ruby 99.90% Shell 0.10%

solr ruby solr-client oop object-oriented

solrb's People

Contributors

Stargazers

Watchers

solrb's Issues

Implement core argument on query running (and other methods).

Make this parameter optional, e.g.

request.run(core: :zh)

Use solrb user agent

Currently Solrb sends this UA:

"User-Agent"=>"Faraday v0.15.2"

It should send "Solrb v#{version}" instead

Create an independent commit command

To be able to commit the changes to solr index.

For example:

1 indexing request
2 indexing request
...
10 indexing request
Commit request (to commit once).

Improve 404 error

Today I was using this gem and it returned 404 error for all my requests. I didn't know why.
Only when I opened the raw_response, I saw that it has this body:

   <html>\n

<head>\n
  <meta http-equiv=\ "Content-Type\" content=\ "text/html;charset=utf-8\"/>\n
  <title>Error 404 Not Found</title>\n
</head>\n

<body>
  <h2>HTTP ERROR 404</h2>\n
  <p>Problem accessing /solr/parts/parts/select. Reason:\n
    <pre>    Not Found</pre>
  </p>\n
</body>\n

</html>

We should be able to see exact 404 message, in this case: "

Problem accessing /solr/parts/parts/select. Reason:\n

    Not Found

Let's not work on it, if it's complex to do w/out an HTML parser

Support multiple cores in configuration

Currently it's only possible to define a single core in configuration:

Solr.configure do |config|
   config.define_core(name: :listings_en) do |f|
     ...
   end
end

However there can be situations when it's necessary to define multiple cores at once, i.e. several cores with identical configurations.

Example:

Solr.configure do |config|
   config.define_cores(names: %w[listings_en listings_pt listings_es] ) do |f|
     ...
   end
end

This configuration type should allow to query different cores and all these core configurations should efficiently reuse the configuration values. That is, there should be only one set of fields in memory, but they should be linked to multiple core names.

@setem @drnluz

UnspecifiedCoreConfig naming may be incorrect

[3] pry(Solr::Support::UrlHelper)> Solr.current_core_config
=> #<Solr::CoreConfiguration::UnspecifiedCoreConfig:0x00007fcedb45a400 @default=false, @fields={}, @name=nil>

This happens when I use a URL to configure Solrb. In that case it says "Unspecified Core Config".

This naming is incorrect I think. It's not possible to work with solr w/out specifying a core. I did specify the core through the URL, so shouldn't say "unspecified".

Support solr cloud

This library doesn't support solr cloud and we should implement it.
Automatic failover should be supported.

Official Solr Java library supports it: https://wiki.apache.org/solr/LBHttpSolrServer
/cc @drnluz @setem

Error when indexing latlng data type

Error: 400 (Bad Request)
ERROR: [doc=6389] Error adding field 'coordinates_ll'='-120.843769,50.7527649' msg=Unable to parse shape given formats "lat,lon", "x y" or as WKT because java.text.ParseException: Unknown Shape definition [-120.843769,50.7527649] (400)

machinio / solrb Goto Github PK

solrb's People

Contributors

Stargazers

Watchers

solrb's Issues

Implement core argument on query running (and other methods).

Use solrb user agent

Create an independent commit command

Improve 404 error

Support multiple cores in configuration

UnspecifiedCoreConfig naming may be incorrect

Support solr cloud

Error when indexing latlng data type

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent