StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20064902
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-19T06:42:40.493
FavoriteCount
0
LastActivityDate
2015-09-05T12:05:37.180
LastEditDate
2015-09-05T12:05:37.180
LastEditorUserId
1144060
OwnerUserId
1144060
ParentId
16835375
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
EDIT: Please keep in mind that this answer is from 2013. The products mentioned here have likely evolved. I have updated the documentation link to reflect changes in the solr clustering wiki. I encourage you to continue your research after reading this information. ORIGINAL: It only really makes sense to run solr on beanstalk instances if you are planning to only ever use the single server deploy. The minute that you want to scale your app you will need to configure your beanstalk environment to either create a <a href="https://cwiki.apache.org/confluence/display/solr/Result+Clustering" rel="nofollow">solr cluster</a> or move to something like CloudSearch. If you are unfamiliar with ec2 lifecycles and solr deployments then CloudSearch will almost certainly save you time (read money). If you do want to run solr on a single instance then you can use rake to launch it by adding a file to your local repo named <code>.ebextensions/solr.config</code> with the following contents: <pre><code>container_commands: 01create_post_dir: command: "mkdir -p /opt/elasticbeanstalk/hooks/appdeploy/post" ignoreErrors: true 02killjava: command: "killall java" test: "ps uax | grep java | grep root" ignoreErrors: true files: "/opt/elasticbeanstalk/hooks/appdeploy/post/99_start_solr.sh": mode: "755" owner: "root" group: "root" content: | #!/usr/bin/env bash . /opt/elasticbeanstalk/support/envvars cd $EB_CONFIG_APP_CURRENT su -c "RAILS_ENV=production bundle exec rake sunspot:solr:start" $EB_CONFIG_APP_USER su -c "RAILS_ENV=production bundle exec rake db:seed" $EB_CONFIG_APP_USER su -c "RAILS_ENV=production bundle exec rake sunspot:reindex" $EB_CONFIG_APP_USER </code></pre> Please keep in mind that this will cause chaos if you are using autoscaling.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSOLR on Elastic Beanstalk
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGardner Bickford
UserOwnerUserId
1. USGardner Bickford
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.