Re: {soft}Commit and cache flusing

[Dmitry Kan]

right. We've got the autoHard commit configured only atm. The soft-commits
are controlled on the client. It was just easier to implement the first
version of our internal commit policy that will commit to all solr
instances at once. This is where we have noticed the reported behavior.


On Wed, Oct 2, 2013 at 9:32 AM, Bram Van Dam  wrote:

> if there are no modifications to an index and a softCommit or hardCommit
 issued, then solr flushes the cache.

>>>
> Indeed. The easiest way to work around this is by disabling auto commits
> and only commit when you have to.
>

Re: Profiling Solr Lucene for query

[Dmitry Kan]

What Shawn has described is exactly what we do: classical distributed
no-SolrCloud setup. This is why it was possible to implement a custom
frontend solr instance.


On Wed, Oct 2, 2013 at 12:42 AM, Shawn Heisey  wrote:

> On 10/1/2013 2:35 PM, Isaac Hebsh wrote:
>
>> Hi Dmitry,
>>
>> I'm trying to examine your suggestion to create a frontend node. It sounds
>> pretty usefull.
>> I saw that every node in solr cluster can serve request for any
>> collection,
>> even if it does not hold a core of that collection. because of that, I
>> thought that adding a new node to the cluster (aka, the frontend/gateway
>> server), and creating a dummy collection (with 1 dummy core), will solve
>> the problem.
>>
>> But, I see that a request which sent to the gateway node, is not then sent
>> to the shards. Instead, the request is proxyed to a (random) core of the
>> requested collection, and from there it is sent to the shards. (It is
>> reasonable, because the SolrCore on the gateway might run with different
>> configuration, etc). This means that my new node isn't functioning as a
>> frontend (which responsible for sorting, etc.), but as a poor load
>> balancer. No performance improvement will come from this implementation.
>>
>> So, how do you suggest to implement a frontend? On the one hand, it has to
>> run a core of the target collection, but on the other hand, we don't want
>> it to hold any shard contents.
>>
>
> With SolrCloud, every node is a frontend node.  If you're running
> SolrCloud, then it doesn't make sense to try and use that concept.
>
> It only makes sense to create a frontend node (or core) if you are using
> traditional distributed search, where you need to include a shards
> parameter.
>
> http://wiki.apache.org/solr/**DistributedSearch
>
> Thanks,
> Shawn
>
>

SolrCloud looses connection to Zookeeper but stays down?

[Henrik Ossipoff Hansen]

We are slowly starting to move from a Master/slave setup into SolrCloud, and 
with the addition some new functionality on our site, we decided to give it a 
go in production (with a very minimal setup so far).

We are experiencing that our nodes looses connection to ZK during the night 
according to the log:

02:17:33 WARN OverseerCollectionProcessor Overseer cannot talk to ZK
02:17:33 WARN Overseer Solr cannot talk to ZK,​ exiting Overseer main queue loop

The node is listed as down in the cloud window in Solr admin. However, as I'm 
speaking, it seems to be able to speak with ZK just fine; I can just fine 
update configurations from ZK to SolrCloud nodes - but the nodes are still 
listed as down. Everything seems to work.

Is this a known bug, that they are still listed as down even though they're up 
and active? We're running 4.4.0.

SolrCloud Nodes infrastucture

[maephisto]

Hi!

I have some foggy stuff on my goggles when i'm looking at SolrCloud, maybe
somebody can help me clear that out!

Let's assume I have a collection that's split in 3 shards. That means i
already have 3 nodes.
Then I also want some replication - replication factor = 2. That's 3 more
nodes.
Zookeeeper it's a must so I'll give it 3 independent machines.

Now, my question is how many machines would I need for that 6 nodes? 
Is it possible to use just 3 machines, each with two Solr instances? Will ZK
then know not to assign the shard replica on the same machine as the shard
leader ?
Even more, is it possible to use just 3 big mean machines, each with a ZK
instance and 2 Solr instances ? Would I be sacrificing performance?

Thanks!



--
View this message in context: 
http://lucene.472066.n3.nabble.com/SolrCloud-Nodes-infrastucture-tp4093097.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: SolrCloud Nodes infrastucture

[Shalin Shekhar Mangar]

Yes, it is possible to use only 3 machines by specifying maxShardsPerNode=2
(default is one). You can even host all six on one machine with
maxShardsPerNode=6 if you want.

The shard allocation won't allocate more than one replica of the same shard
on the same node if it can be helped. It will log a warning if it does that
because of maxShardsPerNode or createNodeSet constraints.

It is possible to use 3 large machines. I know plenty of users are using it
that way. It is hard to say anything about performance. You must benchmark
on your own machines, with your own data and queries.


On Wed, Oct 2, 2013 at 3:45 PM, maephisto  wrote:

> Hi!
>
> I have some foggy stuff on my goggles when i'm looking at SolrCloud, maybe
> somebody can help me clear that out!
>
> Let's assume I have a collection that's split in 3 shards. That means i
> already have 3 nodes.
> Then I also want some replication - replication factor = 2. That's 3 more
> nodes.
> Zookeeeper it's a must so I'll give it 3 independent machines.
>
> Now, my question is how many machines would I need for that 6 nodes?
> Is it possible to use just 3 machines, each with two Solr instances? Will
> ZK
> then know not to assign the shard replica on the same machine as the shard
> leader ?
> Even more, is it possible to use just 3 big mean machines, each with a ZK
> instance and 2 Solr instances ? Would I be sacrificing performance?
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-Nodes-infrastucture-tp4093097.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>



-- 
Regards,
Shalin Shekhar Mangar.

[Schemaless mode] Solr admin - core schema exception

[Alessandro Benedetti]

Hi guys, I think this is a very simple bug, but i didn't know where to
quickly post it :

In the schemaless mode, in the solr admin, if you select a Core and then
select the schema tab, a wild error will appear, because no schema.xml file
exists :

http://localhost:8983/solr/collection1/admin/file?file=*null*
&contentType=text/xml;charset=utf-8

Simply running the example schemaless mode .
I suppose that analyzing the schema type mode, it will be possible to avoid
this error and show the real schema, as the schema browser does ( but is
still necessary the schema button when we have the schema browser ? )

Cheers
-- 
--

Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti

"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"

William Blake - Songs of Experience -1794 England

Re: SolrCloud Nodes infrastucture

[maephisto]

Thank you Shalin!

Let's assume that this configuration is all set up, 3 machines each with 2
Solr instances and a Zk, and I have for collection1 3 shards and 3 replicas.
What if I want to add one more collection, sharded in 3 shards with a
replicationFactor=2 ? 

How can I do this, can it be done dinamically using the CoreAPI? do I need
to go to each solr instance and add the new core or can it be somehow
propagated?



--
View this message in context: 
http://lucene.472066.n3.nabble.com/SolrCloud-Nodes-infrastucture-tp4093097p4093109.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: SolrCloud Nodes infrastucture

[Shalin Shekhar Mangar]

You can use the Collections API to dynamically create the collection.

See https://cwiki.apache.org/confluence/display/solr/Collections+API


On Wed, Oct 2, 2013 at 4:49 PM, maephisto  wrote:

> Thank you Shalin!
>
> Let's assume that this configuration is all set up, 3 machines each with 2
> Solr instances and a Zk, and I have for collection1 3 shards and 3
> replicas.
> What if I want to add one more collection, sharded in 3 shards with a
> replicationFactor=2 ?
>
> How can I do this, can it be done dinamically using the CoreAPI? do I need
> to go to each solr instance and add the new core or can it be somehow
> propagated?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-Nodes-infrastucture-tp4093097p4093109.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>



-- 
Regards,
Shalin Shekhar Mangar.

Re: Problems with maxShardsPerNode in 4.5

[Shalin Shekhar Mangar]

I have committed a fix for 4.6

http://issues.apache.org/jira/browse/SOLR-5295


On Wed, Oct 2, 2013 at 10:34 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> Thanks for reporting this Brett. This is indeed a bug. A workaround is to
> specify replicationFactor=1 with the createShard command which will create
> only one replica even if maxShardsPerNode=1000 at collection level.
>
> I'll open an issue.
>
>
> On Wed, Oct 2, 2013 at 7:25 AM, Brett Hoerner wrote:
>
>> Related, 1 more try:
>>
>> Created collection starting with 4 shards on 1 box. Had to set
>> maxShardsPerNode to 4 to do this.
>>
>> Now I want to "roll over" my time window, so to attempt to deal with the
>> problems noted above I delete the oldest shard first. That works fine.
>>
>> Now I try to add my new shard, which works, but again it defaults to
>> "maxShardsPerNode" # of replicas, so I'm left with:
>>
>> * [deleted by me] hour0
>> * hour1 - 1 replica
>> * hour2 - 1 replica
>> * hour3 - 1 replica
>> * hour4 - 4 replicas [ << the one I created after deleting hour0]
>>
>> Still at a loss as to how I would create 1 new shard with 1 replica on any
>> server in 4.5?
>>
>> Thanks!
>>
>>
>> On Tue, Oct 1, 2013 at 8:14 PM, Brett Hoerner > >wrote:
>>
>> > It seems that changes in 4.5 collection configuration now require users
>> to
>> > set a maxShardsPerNode (or it defaults to 1).
>> >
>> > Maybe this was the case before, but with the new CREATESHARD API it
>> seems
>> > a very restrictive. I've just created a very simple test collection on 3
>> > machines where I set maxShardsPerNode at collection creation time to 1,
>> and
>> > I made 3 shards. Everything is good.
>> >
>> > Now I want a 4th shard, it seems impossible to create because the
>> cluster
>> > "knows" I should only have 1 shard per node. Yet my problem doesn't
>> require
>> > more hardware, I just my new shard to exist on one of the existing
>> servers.
>> >
>> > So I try again -- I create a collection with 3 shards and set
>> > maxShardsPerNode to 1000 (just as a silly test). Everything is good.
>> >
>> > Now I add shard4 and it immediately tries to add 1000 replicas of
>> shard4...
>> >
>> > You can see my earlier email today about time-oriented data in 4.5 to
>> see
>> > what I'm trying to do. I was hoping to have 1 shard per hour/day with
>> the
>> > ability to easily add/drop them as I move the time window (say, a week
>> of
>> > data, 1 per day).
>> >
>> > Am I missing something?
>> >
>> > Thanks!
>> >
>>
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>



-- 
Regards,
Shalin Shekhar Mangar.

UML diagrams for solr

[Nutan]

Hello,
I need UML diagrams(class,component,deployment,architecture diagrams) for
Solr, where can I get these diagrams?
Any help will be appreciated.




--
View this message in context: 
http://lucene.472066.n3.nabble.com/UML-diagrams-for-solr-tp4093126.html
Sent from the Solr - User mailing list archive at Nabble.com.

Configure Solr to use http proxy for querying shards?

[Dan Bolser]

Hi,

I'm running my Solr server on a box which can only see 'the web' via
an http proxy. For most applications it's as simple as setting
http_proxy in the shell environment to get them to see the 'the web'.
However, this isn't working for Solr.

The reason this is an issue is because my Solr server is configured to
perform a sharded query across multiple sites on the web, i.e. I have
this in my solrconfig.xml:

  

  ...
  
  site.out.there/solr/core,etc.like.this/solr/core
  
  true
  

When I try to run a query against my server running on this box, I get
the following errors:
"error":"org.apache.http.conn.HttpHostConnectException: Connection to
http://sites.out.there refused",
  "trace":"...


Can I get Solr to use the http proxy, or am I stuck?


Cheers,
Dan.

upgrading from Solr 3.5 to Solr 4.X

[subacini Arunkumar]

Hi Solr Team,

We are planning to upgrade from Solr 3.5 to Solr 4.x version. Appreciate if
you can provide any pointers/documentation on step by step by changes.

Also, the reason  for upgrading is to use Solr join [not solr cloud or any
other feature]. So which version is better Solr 4.0 or higher version
considering the changes to be minimal during upgradation.


Thanks,
Subacini

Re: Configure Solr to use http proxy for querying shards?

[Dan Bolser]

In answer to my own question (with help from steffkes in IRC):

Solr doesn't allow for proxy configuration, however, you can configure
the proxy used by the JVM, and Solr uses the
'SystemDefaultHttpClient', i.e.

java -jar start.jar\
  -Dhttp.proxyHost=our.proxy.boxy -Dhttp.proxyPort=8080


Cheers,
Dan.

On 2 October 2013 12:32, Dan Bolser  wrote:
> Hi,
>
> I'm running my Solr server on a box which can only see 'the web' via
> an http proxy. For most applications it's as simple as setting
> http_proxy in the shell environment to get them to see the 'the web'.
> However, this isn't working for Solr.
>
> The reason this is an issue is because my Solr server is configured to
> perform a sharded query across multiple sites on the web, i.e. I have
> this in my solrconfig.xml:
>
>default="true" startup="lazy">
> 
>   ...
>   
>name="shards">site.out.there/solr/core,etc.like.this/solr/core
>   
>   true
>   
>
> When I try to run a query against my server running on this box, I get
> the following errors:
> "error":"org.apache.http.conn.HttpHostConnectException: Connection to
> http://sites.out.there refused",
>   "trace":"...
>
>
> Can I get Solr to use the http proxy, or am I stuck?
>
>
> Cheers,
> Dan.

Next official Solr release

[Simon Zeng]

Hi Solr team,

I am working on a project that needs Solr 'block join' feature that currently 
available in 4.6 nightly build. My boss feel more comfortable with an
official release like 4.4.  I am wondering if there is any target release date 
for Solr 4.6(+) or 5.0?

Thanks,
Simon

Re: Next official Solr release

[Shawn Heisey]

On 10/1/2013 10:21 PM, Simon Zeng wrote:
> I am working on a project that needs Solr 'block join' feature that currently 
> available in 4.6 nightly build. My boss feel more comfortable with an
> official release like 4.4.  I am wondering if there is any target release 
> date for Solr 4.6(+) or 5.0?

There is a strong push to keep the release branch (currently branch_4x)
in a state where it can always be used in place of a full release.
Breakage does sometimes happen, but it's usually detectable by running
the large suite of unit tests that are part of the source code.  When
something does break, it is typically fixed very quickly.  It's
development code, and the pace of change in the Lucene/Solr project is
VERY fast.

The process to release 4.5 is wrapping up as I type this.  The release
vote passed, so the release candidate will be finalized and start
copying to download mirrors.  It is likely to be only a few more days
before the release announcement is made.  You can probably get it before
the announcement is made by checking the parent directory on a download
mirror.

Nothing is set in stone.  There's no set schedule for releases.  Since
the 4.0 release, minor releases are dropping about once every 1-3
months.  Two of those minor releases were quickly followed by point
releases to fix some bigger bugs.  Releases happen when one of the
committers decides that it's time and takes the reins to act as release
manager.  We don't ignore the community, so if there are strong voices
wanting a release, it's likely to happen.

A 4.6.0 release will probably happen before the end of the year, but I
can't guarantee that.

The release timeframe for 5.0 is *completely* undecided.  It might be a
few months from now, it might be a year from now.  Some of the things
that have been tentatively planned for that release are nowhere near
finished.

Thanks,
Shawn

Re: upgrading from Solr 3.5 to Solr 4.X

[Shawn Heisey]

On 10/2/2013 1:08 AM, subacini Arunkumar wrote:
> We are planning to upgrade from Solr 3.5 to Solr 4.x version. Appreciate if
> you can provide any pointers/documentation on step by step by changes.
> 
> Also, the reason for upgrading is to use Solr join [not solr cloud or any
> other feature]. So which version is better Solr 4.0 or higher version
> considering the changes to be minimal during upgradation.

When it comes to open source software, it's usually best to run the
latest version.  If there's a major problem with a particular release,
it will be *QUICKLY* followed by a point release to fix those problems,
or a workaround will be prominently posted.  When new releases happen
after that, it's best to start testing with it right away and upgrade
your production install as soon as you feel comfortable with it.  If the
latest version just came out, you might want to start with one version
back, but plan on upgrading to the latest version quickly afterwards.

The 4.0.0 release came out on October 12, 2012.  That's one year ago.
There have been six releases since then, and a seventh (4.5.0) is days
from announcement.

Every release comes with a CHANGES.txt file, where individual issues are
listed and important upgrade notes are given.  It's also a good idea to
compare the example config/schema from the version you're running to the
example config/schema in the new version in order to see what has
changed there, for clues about how you might want to change your own
configuration.

When upgrading major releases, it is probably a good idea to start with
the example config/schema and make changes until it does what you need.
 It's also a *very* good idea to build up a complete system in a dev
environment so you can run extensive tests without making any changes to
your production setup.

Finally, stay subscribed to this mailing list, the user list.  Typical
problems and bugs are very likely to be discussed here.  If you want to
get down and dirty and don't mind a lot of email traffic, you can also
join the dev list.

Thanks,
Shawn

Re: SolrCloud Nodes infrastucture

[Shawn Heisey]

On 10/2/2013 4:15 AM, maephisto wrote:
> Even more, is it possible to use just 3 big mean machines, each with a ZK
> instance and 2 Solr instances ? Would I be sacrificing performance?

To supplement the replies you've already gotten:  Don't run more that
one Solr instance per machine.  One Solr instance is perfectly capable
of handling many collections and shard replicas.  The maxShardsPerNode
parameter you've been given controls how many shards can live on one
Solr instance, a node does not necessarily refer to a machine.

Unless you are very very careful, understand things on a very deep
level, and do many things manually that can normally be automated,
running more than one instance per machine just causes administrative
headaches and unexpected behavior.  Don't do it, unless what you want to
do is run more than one independent SolrCloud on one set of hardware and
zookeeper ensemble.

Thanks,
Shawn

Submitting Multiple JSON documents from Solr Admin Documents

[Dennis Brundage]

Is it possible to submit multiple JSON documents through the Solr Admin
Documents page?

The default json is: {"id":"change.me","title":"change.me"}. If I try to add
a second document such as {"id":"change.me2","title":"change.me"}, and
submit them together, I get parsing errors.  I have tried:

1.
{"id":"change.me","title":"change.me"}{"id":"change2.me","title":"change.me2"}
2.
{{"id":"change.me","title":"change.me"}{"id":"change2.me","title":"change.me2"}}
3.
{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}
4.
{{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}}

The parsing errors for items 2, 3 and 4 are (the parsing error for 1
indicates the need for either "," or "}" after the first json document.

"msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
AFTER='\"id\":\"change.me\",\"title\":\"change.me\"}{\"'",

"msg": "Expected string: char={,position=54 BEFORE='{\"add\":{
\"doc\":{\"id\":\"change.me\",\"title\":\"change.me\"},{'
AFTER='\"id\":\"change.me2\",\"title\":\"change.me\"},'",

"msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
AFTER='\"id\":\"change.me\",\"title\":\"change.me\"},{'",




--
View this message in context: 
http://lucene.472066.n3.nabble.com/Submitting-Multiple-JSON-documents-from-Solr-Admin-Documents-tp4093155.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Problems with maxShardsPerNode in 4.5

[Brett Hoerner]

Shalin,

Thanks for the fix. There's still part of the underlying issue that I
consider a bug or a documentation problem: how do I adjust maxShardsPerNode
after my collection has been created, and/or how can I disable it being
checked/used at all? It seems odd to me that I have to set it to an odd
number like 1000 just to get around this?

Thanks!


On Wed, Oct 2, 2013 at 12:04 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> Thanks for reporting this Brett. This is indeed a bug. A workaround is to
> specify replicationFactor=1 with the createShard command which will create
> only one replica even if maxShardsPerNode=1000 at collection level.
>
> I'll open an issue.
>
>
> On Wed, Oct 2, 2013 at 7:25 AM, Brett Hoerner  >wrote:
>
> > Related, 1 more try:
> >
> > Created collection starting with 4 shards on 1 box. Had to set
> > maxShardsPerNode to 4 to do this.
> >
> > Now I want to "roll over" my time window, so to attempt to deal with the
> > problems noted above I delete the oldest shard first. That works fine.
> >
> > Now I try to add my new shard, which works, but again it defaults to
> > "maxShardsPerNode" # of replicas, so I'm left with:
> >
> > * [deleted by me] hour0
> > * hour1 - 1 replica
> > * hour2 - 1 replica
> > * hour3 - 1 replica
> > * hour4 - 4 replicas [ << the one I created after deleting hour0]
> >
> > Still at a loss as to how I would create 1 new shard with 1 replica on
> any
> > server in 4.5?
> >
> > Thanks!
> >
> >
> > On Tue, Oct 1, 2013 at 8:14 PM, Brett Hoerner  > >wrote:
> >
> > > It seems that changes in 4.5 collection configuration now require users
> > to
> > > set a maxShardsPerNode (or it defaults to 1).
> > >
> > > Maybe this was the case before, but with the new CREATESHARD API it
> seems
> > > a very restrictive. I've just created a very simple test collection on
> 3
> > > machines where I set maxShardsPerNode at collection creation time to 1,
> > and
> > > I made 3 shards. Everything is good.
> > >
> > > Now I want a 4th shard, it seems impossible to create because the
> cluster
> > > "knows" I should only have 1 shard per node. Yet my problem doesn't
> > require
> > > more hardware, I just my new shard to exist on one of the existing
> > servers.
> > >
> > > So I try again -- I create a collection with 3 shards and set
> > > maxShardsPerNode to 1000 (just as a silly test). Everything is good.
> > >
> > > Now I add shard4 and it immediately tries to add 1000 replicas of
> > shard4...
> > >
> > > You can see my earlier email today about time-oriented data in 4.5 to
> see
> > > what I'm trying to do. I was hoping to have 1 shard per hour/day with
> the
> > > ability to easily add/drop them as I move the time window (say, a week
> of
> > > data, 1 per day).
> > >
> > > Am I missing something?
> > >
> > > Thanks!
> > >
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>

Re: Submitting Multiple JSON documents from Solr Admin Documents

[Stefan Matheis]

Dennis

Have a look at the wiki .. last code-block in the section: 
http://wiki.apache.org/solr/UpdateJSON#Example

-Stefan 


On Wednesday, October 2, 2013 at 5:46 PM, Dennis Brundage wrote:

> Is it possible to submit multiple JSON documents through the Solr Admin
> Documents page?
> 
> The default json is: {"id":"change.me (http://change.me)","title":"change.me 
> (http://change.me)"}. If I try to add
> a second document such as {"id":"change.me2","title":"change.me 
> (http://change.me)"}, and
> submit them together, I get parsing errors. I have tried:
> 
> 1.
> {"id":"change.me (http://change.me)","title":"change.me 
> (http://change.me)"}{"id":"change2.me 
> (http://change2.me)","title":"change.me2"}
> 2.
> {{"id":"change.me (http://change.me)","title":"change.me 
> (http://change.me)"}{"id":"change2.me 
> (http://change2.me)","title":"change.me2"}}
> 3.
> {"id":"change.me (http://change.me)","title":"change.me 
> (http://change.me)"},{"id":"change2.me 
> (http://change2.me)","title":"change.me2"}
> 4.
> {{"id":"change.me (http://change.me)","title":"change.me 
> (http://change.me)"},{"id":"change2.me 
> (http://change2.me)","title":"change.me2"}}
> 
> The parsing errors for items 2, 3 and 4 are (the parsing error for 1
> indicates the need for either "," or "}" after the first json document.
> 
> "msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
> AFTER='\"id\":\"change.me (http://change.me)\",\"title\":\"change.me 
> (http://change.me)\"}{\"'",
> 
> "msg": "Expected string: char={,position=54 BEFORE='{\"add\":{
> \"doc\":{\"id\":\"change.me (http://change.me)\",\"title\":\"change.me 
> (http://change.me)\"},{'
> AFTER='\"id\":\"change.me2\",\"title\":\"change.me (http://change.me)\"},'",
> 
> "msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
> AFTER='\"id\":\"change.me (http://change.me)\",\"title\":\"change.me 
> (http://change.me)\"},{'",
> 
> 
> 
> 
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/Submitting-Multiple-JSON-documents-from-Solr-Admin-Documents-tp4093155.html
> Sent from the Solr - User mailing list archive at Nabble.com 
> (http://Nabble.com).
> 
> 

Re: Submitting Multiple JSON documents from Solr Admin Documents

[Stefan Matheis]

Hm, actually this post made me think, perhaps it would be a good idea to 
integrate some kind of client-side validation? So we could report back at least 
those "basic" JSON-format errors?

-Stefan 


On Wednesday, October 2, 2013 at 6:15 PM, Stefan Matheis wrote:

> Dennis
> 
> Have a look at the wiki .. last code-block in the section: 
> http://wiki.apache.org/solr/UpdateJSON#Example
> 
> -Stefan 
> 
> On Wednesday, October 2, 2013 at 5:46 PM, Dennis Brundage wrote:
> 
> > Is it possible to submit multiple JSON documents through the Solr Admin
> > Documents page?
> > 
> > The default json is: {"id":"change.me 
> > (http://change.me)","title":"change.me (http://change.me)"}. If I try to add
> > a second document such as {"id":"change.me2","title":"change.me 
> > (http://change.me)"}, and
> > submit them together, I get parsing errors. I have tried:
> > 
> > 1.
> > {"id":"change.me (http://change.me)","title":"change.me 
> > (http://change.me)"}{"id":"change2.me 
> > (http://change2.me)","title":"change.me2"}
> > 2.
> > {{"id":"change.me (http://change.me)","title":"change.me 
> > (http://change.me)"}{"id":"change2.me 
> > (http://change2.me)","title":"change.me2"}}
> > 3.
> > {"id":"change.me (http://change.me)","title":"change.me 
> > (http://change.me)"},{"id":"change2.me 
> > (http://change2.me)","title":"change.me2"}
> > 4.
> > {{"id":"change.me (http://change.me)","title":"change.me 
> > (http://change.me)"},{"id":"change2.me 
> > (http://change2.me)","title":"change.me2"}}
> > 
> > The parsing errors for items 2, 3 and 4 are (the parsing error for 1
> > indicates the need for either "," or "}" after the first json document.
> > 
> > "msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
> > AFTER='\"id\":\"change.me (http://change.me)\",\"title\":\"change.me 
> > (http://change.me)\"}{\"'",
> > 
> > "msg": "Expected string: char={,position=54 BEFORE='{\"add\":{
> > \"doc\":{\"id\":\"change.me (http://change.me)\",\"title\":\"change.me 
> > (http://change.me)\"},{'
> > AFTER='\"id\":\"change.me2\",\"title\":\"change.me (http://change.me)\"},'",
> > 
> > "msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
> > AFTER='\"id\":\"change.me (http://change.me)\",\"title\":\"change.me 
> > (http://change.me)\"},{'",
> > 
> > 
> > 
> > 
> > --
> > View this message in context: 
> > http://lucene.472066.n3.nabble.com/Submitting-Multiple-JSON-documents-from-Solr-Admin-Documents-tp4093155.html
> > Sent from the Solr - User mailing list archive at Nabble.com 
> > (http://Nabble.com).
> > 
> > 
> > 
> 
> 

Re: Submitting Multiple JSON documents from Solr Admin Documents

[Jack Krupansky]

Use square brackets (array) around a list of documents:

[{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}]

-- Jack Krupansky

-Original Message- 
From: Dennis Brundage

Sent: Wednesday, October 02, 2013 11:46 AM
To: solr-user@lucene.apache.org
Subject: Submitting Multiple JSON documents from Solr Admin Documents

Is it possible to submit multiple JSON documents through the Solr Admin
Documents page?

The default json is: {"id":"change.me","title":"change.me"}. If I try to add
a second document such as {"id":"change.me2","title":"change.me"}, and
submit them together, I get parsing errors.  I have tried:

1.
{"id":"change.me","title":"change.me"}{"id":"change2.me","title":"change.me2"}
2.
{{"id":"change.me","title":"change.me"}{"id":"change2.me","title":"change.me2"}}
3.
{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}
4.
{{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}}

The parsing errors for items 2, 3 and 4 are (the parsing error for 1
indicates the need for either "," or "}" after the first json document.

"msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
AFTER='\"id\":\"change.me\",\"title\":\"change.me\"}{\"'",

"msg": "Expected string: char={,position=54 BEFORE='{\"add\":{
\"doc\":{\"id\":\"change.me\",\"title\":\"change.me\"},{'
AFTER='\"id\":\"change.me2\",\"title\":\"change.me\"},'",

"msg": "Expected string: char={,position=16 BEFORE='{\"add\":{ \"doc\":{{'
AFTER='\"id\":\"change.me\",\"title\":\"change.me\"},{'",




--
View this message in context: 
http://lucene.472066.n3.nabble.com/Submitting-Multiple-JSON-documents-from-Solr-Admin-Documents-tp4093155.html
Sent from the Solr - User mailing list archive at Nabble.com. 

Re: Submitting Multiple JSON documents from Solr Admin Documents

[Dennis Brundage]

After putting brackets around the doucments:

[{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}]
 

I get the following error:

"msg": "Expected: OBJECT_START but got ARRAY_START at [16]",


I can submit multiple documents using post.jar, but was curious if there is
some trick that I am missing to get it working on the Solr Admin Documents
page (http://localhost:8983/solr/#/collection1/documents). I am using the
Solr 4.4 example server.





--
View this message in context: 
http://lucene.472066.n3.nabble.com/Submitting-Multiple-JSON-documents-from-Solr-Admin-Documents-tp4093155p4093170.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Submitting Multiple JSON documents from Solr Admin Documents

[Chris Hostetter]

: After putting brackets around the doucments:
: 
: 
[{"id":"change.me","title":"change.me"},{"id":"change2.me","title":"change.me2"}]
 
: 
: I get the following error:


There are two ways of submitting JSON using the /documents screen...

1) select "JSON" from the pulldown...

this accepts only a single JSON document to be added, because it wraps 
it in tags like so...

{"add":{ "doc": YOUR_TEXT_AREA_INPUT,
 "boost": BOOST_FORM_INPUT,
 "overwrite": CHECKBOX_INPUT,
 "commitWithin": COMMIT_WITHIN_FORM_INPUT } }

(likewise, similar wrapper tags are added if you select "XML" from the 
pulldown)

2) select "Solr command (raw XML or JSON)" from the pulldown...

this accepts any arbitrary xml or json you wish to post, and you can do 
multiple documents using the json array notation -- the UI doesn't touch 
what you give it at all.


(NOTE: if you change the "Update Handler" text box at teh top of the page 
to "/debug/dump" -- using the example configs -- you can see solr echo 
back exactly what the UI is sending when you submit the form)


-Hoss

Re: Next official Solr release

[Chris Hostetter]

: I am working on a project that needs Solr 'block join' feature that 
: currently available in 4.6 nightly build. My boss feel more comfortable 
: with an

FWIW: block join is in 4.5 which should hit the mirrors this week...

https://issues.apache.org/jira/browse/SOLR-3076




-Hoss

Re: Problems with maxShardsPerNode in 4.5

[Shalin Shekhar Mangar]

You are right Brett. There's plenty more to be done. I can't promise when
all these improvements will be done but at least some should make it to 4.6

https://issues.apache.org/jira/browse/SOLR-5128


On Wed, Oct 2, 2013 at 9:35 PM, Brett Hoerner wrote:

> Shalin,
>
> Thanks for the fix. There's still part of the underlying issue that I
> consider a bug or a documentation problem: how do I adjust maxShardsPerNode
> after my collection has been created, and/or how can I disable it being
> checked/used at all? It seems odd to me that I have to set it to an odd
> number like 1000 just to get around this?
>
> Thanks!
>
>
> On Wed, Oct 2, 2013 at 12:04 AM, Shalin Shekhar Mangar <
> shalinman...@gmail.com> wrote:
>
> > Thanks for reporting this Brett. This is indeed a bug. A workaround is to
> > specify replicationFactor=1 with the createShard command which will
> create
> > only one replica even if maxShardsPerNode=1000 at collection level.
> >
> > I'll open an issue.
> >
> >
> > On Wed, Oct 2, 2013 at 7:25 AM, Brett Hoerner  > >wrote:
> >
> > > Related, 1 more try:
> > >
> > > Created collection starting with 4 shards on 1 box. Had to set
> > > maxShardsPerNode to 4 to do this.
> > >
> > > Now I want to "roll over" my time window, so to attempt to deal with
> the
> > > problems noted above I delete the oldest shard first. That works fine.
> > >
> > > Now I try to add my new shard, which works, but again it defaults to
> > > "maxShardsPerNode" # of replicas, so I'm left with:
> > >
> > > * [deleted by me] hour0
> > > * hour1 - 1 replica
> > > * hour2 - 1 replica
> > > * hour3 - 1 replica
> > > * hour4 - 4 replicas [ << the one I created after deleting hour0]
> > >
> > > Still at a loss as to how I would create 1 new shard with 1 replica on
> > any
> > > server in 4.5?
> > >
> > > Thanks!
> > >
> > >
> > > On Tue, Oct 1, 2013 at 8:14 PM, Brett Hoerner  > > >wrote:
> > >
> > > > It seems that changes in 4.5 collection configuration now require
> users
> > > to
> > > > set a maxShardsPerNode (or it defaults to 1).
> > > >
> > > > Maybe this was the case before, but with the new CREATESHARD API it
> > seems
> > > > a very restrictive. I've just created a very simple test collection
> on
> > 3
> > > > machines where I set maxShardsPerNode at collection creation time to
> 1,
> > > and
> > > > I made 3 shards. Everything is good.
> > > >
> > > > Now I want a 4th shard, it seems impossible to create because the
> > cluster
> > > > "knows" I should only have 1 shard per node. Yet my problem doesn't
> > > require
> > > > more hardware, I just my new shard to exist on one of the existing
> > > servers.
> > > >
> > > > So I try again -- I create a collection with 3 shards and set
> > > > maxShardsPerNode to 1000 (just as a silly test). Everything is good.
> > > >
> > > > Now I add shard4 and it immediately tries to add 1000 replicas of
> > > shard4...
> > > >
> > > > You can see my earlier email today about time-oriented data in 4.5 to
> > see
> > > > what I'm trying to do. I was hoping to have 1 shard per hour/day with
> > the
> > > > ability to easily add/drop them as I move the time window (say, a
> week
> > of
> > > > data, 1 per day).
> > > >
> > > > Am I missing something?
> > > >
> > > > Thanks!
> > > >
> > >
> >
> >
> >
> > --
> > Regards,
> > Shalin Shekhar Mangar.
> >
>



-- 
Regards,
Shalin Shekhar Mangar.

Re: Unable to deplay solr 4.3.0 on jboss EAP 6.1 in mode full JavaEE 6

[delkant]

Did you solve this problem?? I'm dealing exactly with the same issue! Please
share the solution if you have it. Thanks!



--
View this message in context: 
http://lucene.472066.n3.nabble.com/Unable-to-deplay-solr-4-3-0-on-jboss-EAP-6-1-in-mode-full-JavaEE-6-tp4084528p4093183.html
Sent from the Solr - User mailing list archive at Nabble.com.

App server?

[Mark]

Is Jetty sufficient for running Solr or should I go with something a little 
more enterprise like tomcat?

Any others?

Re: App server?

[Tim Vaillancourt]

Jetty should be sufficient, and is the more-common container for Solr.
Also, Solr tests are written for Jetty.

Lastly, I'd argue Jetty is just-as "enterprise" as Tomcat. Google App
Engine (running lots of enterprise), is Jetty-based, for example.

Cheers,

Tim


On 2 October 2013 15:44, Mark  wrote:

> Is Jetty sufficient for running Solr or should I go with something a
> little more enterprise like tomcat?
>
> Any others?

Re: App server?

[Otis Gospodnetic]

We run all our stuff (solr and everything else webappy) under Jetty. Never
Tomcat.

Otis
Solr & ElasticSearch Support
http://sematext.com/
On Oct 2, 2013 6:45 PM, "Mark"  wrote:

> Is Jetty sufficient for running Solr or should I go with something a
> little more enterprise like tomcat?
>
> Any others?

Re: Highlighting question

[ewinclub7]

อันดับแรกให้เช็คก่อนว่า คุณมีจำนวนเงินขั้นต่ำพอที่จะถอนหรือไม่
ก้าวขึ้นมาครองใจผู้บริโภคดีที่สุดในประเทศไทย
ยิ่งเป็นกลุ่มคนสมัยใหม่แล้วยิ่งชอบ
แต่เมื่อนักเล่นสมัยใหม่ได้สัมผัสกับวิธีเล่นออนไลน์แล้ว
ทำให้นักเล่นมีความชื่นชมชื่นชอบเป็นอย่างยิ่ง  พนันบอล
   เป็นผู้ให้คำแนะนำออนไลน์
และยังได้รับรองมาตราฐานสากล มีใบอนุญาตการให้แนวทางอย่างถูกฏหมาย 
เช็คผลบอลวันนี้   
และเราไม่ประสงค์จะให้บุคคลใดกระทำการช่อโกงหรือส่อไปในทางช่อโกงกับเราในทุกรูปแบบ 
บาคาร่า   
ที่จะทำให้ผู้เล่นเกิดความไว้วางใจมากขึ้นจากการเล่นพนันในฐานะการเรียนรู้รับประสบการณ์ใหม่ๆจากรูปแบบของการแทงในวิถีของการออนไลน์ล่ะค่ะ
หลังจาก Login ท่านสามารถตรวจสอบ ยอดเงินของท่าน ใน ยอดคงเหลือ
ในเมนูด้านบนหรือวางพนันฟุตบอลในเมนูกีฬาด้านซ้ายมือ
เรายืนยันได้ว่าทางเราไม่มีการควบคุมเกมส์ และผลที่จะเกิดขึ้นของเกมส์ต่างๆ
หากคุณต้องการที่จะตรวจสอบเราก่อนที่คุณจะเล่นด้วยเงินจริง  แทงบอลสเต็ป
   แน่นอนว่าคนเราหากเล่น
คาสิโนออนไลน์ แล้วชนะได้เล่นชนะได้เล่นรางวัลแล้ว  สมัครบาคาร่า
   คุณมั่นใจเราได้
เราใช้นวัตกรรมเทคโนโลยีเกมส์ออนไลน์
ที่ได้รับมาตราฐานมีความปลอดภัยด้วยการใช้เทคโนโลยีที่ซับซ้อนในการเข้ารหัส
รวมทั้งไฟร์วอลล์และเทคโนโลยีป้องกันความปลอดภัยของรายละเอียดส่วนบุคคล



--
View this message in context: 
http://lucene.472066.n3.nabble.com/Highlighting-question-tp501425p4093238.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Unable to deplay solr 4.3.0 on jboss EAP 6.1 in mode full JavaEE 6

[Roland Everaert]

No, I have not. I am now working on something else, and I really don't know
how to investigate this problem :(


On Wed, Oct 2, 2013 at 8:24 PM, delkant  wrote:

> Did you solve this problem?? I'm dealing exactly with the same issue!
> Please
> share the solution if you have it. Thanks!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Unable-to-deplay-solr-4-3-0-on-jboss-EAP-6-1-in-mode-full-JavaEE-6-tp4084528p4093183.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

Re: App server?

[Furkan KAMACI]

I've answered a similar question before as like yours. Here is my thoughts:

Of course you may have some reasons to use Tomcat or anything else (i.e.
your stuff may have more experience at Tomcat etc.) However developers
generally runsJetty because it is default for Solr and I should point that
Solr unit tests run against jetty (in fact, a specific version of Jetty)
and well tested (if you search in mail list you can find some conversations
about it). If you follow Solr developer list you may realize using a well
tested container or not. For example:
https://issues.apache.org/jira/browse/SOLR-4716
 and
https://issues.apache.org/jira/browse/SOLR-4584?focusedCommentId=13625276&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13625276
 can show that there maybe some bugs for non Jetty containers and if you
choose any other container except for Jetty you can hit one of them.

If you want to look at the comparison of Jetty vs. Tomcat I suggest you
look at here:

http://www.openlogic.com/wazi/bid/257366/Power-Java-based-web-apps-with-
Jetty-application-server


and here:

http://www.infoq.com/news/2009/08/google-chose-jetty


2013/10/3 Otis Gospodnetic 

> We run all our stuff (solr and everything else webappy) under Jetty. Never
> Tomcat.
>
> Otis
> Solr & ElasticSearch Support
> http://sematext.com/
> On Oct 2, 2013 6:45 PM, "Mark"  wrote:
>
> > Is Jetty sufficient for running Solr or should I go with something a
> > little more enterprise like tomcat?
> >
> > Any others?
>