Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Parameter Name

Description

Default value

type

Specifies the SolrClient implementation to use. This is a string value of one of the following cloud or http. The values represent CloudSolrServer or HttpSolrServer respectively.

http

url

Defines the fully qualified URL of Solr into which data should be indexed. Multiple URL can be provided using comma as a delimiter. When the value of type property is cloud, the URL should not include any collections or cores; just the root Solr path.

http://localhost:8983/solr/nutch

collection

The collection used in requests. Only used when the value of type property is cloud.


weight.field

Field's name where the weight of the documents will be written. If it is empty no field will be used.


commitSize

Defines the number of documents to send to Solr in a single update batch. Decrease when handling very large documents to prevent Nutch from running out of memory.

Note:
Note

It does not explicitly trigger a server side commit.


1000

auth

Whether to enable HTTP basic authentication for communicating with Solr. Use the username and password properties to configure your credentials.

false

username

The username of Solr server.

username

password

The password of Solr server.

password

...

Parameter Name

Description

Default value

server.uri

URI with connection parameters in the form amqp://<username>:<password>@<hostname>:<port>/<virtualHost>
Where: <<Include(IndexWriters/RabbitURIParts)>>

amqp://guest:guest@localhost:5672/

binding

Whether the relationship between an exchange and a queue is created automatically.
NOTE:

  • <username> is the username for RabbitMQ server.
  • <password> is the password for RabbitMQ server.
  • <hostname> is where the RabbitMQ server is running.
  • <port> is where the RabbitMQ server is listening.
  • <virtualHost> is where the exchange is and the user has access.

amqp://guest:guest@localhost:5672/

binding

Whether the relationship between an exchange and a queue is created automatically.

Note

Binding between exchanges is not supported.


false

binding.arguments

Arguments used in binding. It must have the form key1=value1,key2=value2. This value is only used when the exchange's type is headers and the value of binding property is true. In other cases is ignored.


exchange.name

Name for the exchange where the messages will be sent.


exchange.options

Options used when the exchange is created. Only used when the value of binding property is true. It must have the form type=<type>,durable=<durable>
Where: <<Include(IndexWriters/RabbitExchangeOptions)>>

  • <type> is direct, topic, headers or fanout
  • <durable> is true or false

type=direct,durable=true

queue.name

Name of the queue used to create the binding. Only used when the value of binding property is true.

nutch.queue

queue.options

Options used when the queue is created. Only used when the value of binding property is true. It must have the form durable=<durable>,exclusive=<exclusive>,auto-delete=<auto-delete>,arguments=<arguments>
Where: <<Include(IndexWriters/RabbitQueueOptions)>>

  • <durable> is true or false
  • <exclusive> is true or false
  • <auto-delete> is true or false
  • <arguments> must be the form key1:value1;key2:value2

durable=true,exclusive=false,auto-delete=false

routingkey

The routing key used to route messages in the exchange. It only makes sense when the exchange type is topic or direct.

Value of queue.name property

commit.mode

single if a message contains only one document. In this case, a header with the action (write, update or delete) will be added. multiple if a message contains all documents.

multiple

commit.size

Amount of documents to send into each message if the value of commit.mode property is multiple. In single mode this value represents the amount of messages to be sent.

250

headers.static

Headers to add to each message. It must have the form key1=value1,key2=value2.


headers.dynamic

Document's fields to add as headers to each message. It must have the form field1,field2. Only used when the value of commit.mode property is single


...