none
cohowinery.com in results URLs RRS feed

  • Question

  • Anybody have any idea why docs indexed via docpush have cohowinery.com in their URLs when displayed in the FAST search screen?

    Thanks, Shane

    Tuesday, June 7, 2011 3:30 PM

Answers

  • Hi Shane,

    As stated on the docpush reference page, cohowinery.com is the default uri prefix for docpush if nothing else is specified with the -u parameter.

    If you want to remove results you added with docpush, then add -d to your docpush command, which will remove the item instead of pushing it.

    Regards,
    Mikael Svenson 


    Search Enthusiast - MCTS SharePoint/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Marked as answer by S h a n e Wednesday, June 8, 2011 8:43 AM
    Tuesday, June 7, 2011 7:25 PM

All replies

  • Hi Shane,

    As stated on the docpush reference page, cohowinery.com is the default uri prefix for docpush if nothing else is specified with the -u parameter.

    If you want to remove results you added with docpush, then add -d to your docpush command, which will remove the item instead of pushing it.

    Regards,
    Mikael Svenson 


    Search Enthusiast - MCTS SharePoint/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Marked as answer by S h a n e Wednesday, June 8, 2011 8:43 AM
    Tuesday, June 7, 2011 7:25 PM
  • Hi Mikael,

    having read the docpush reference page I'm still not 100% sure what to put as the -u parameter for file share files. The example given is to use -g file:/// - is this what I should use and leave out the -u parameter altogether?

    Thanks, Shane

     

    Tuesday, June 7, 2011 8:01 PM
  • Hi Shane,

    If you want to index files from file shares, add a content source on your Content SSA of type File Share, and put in the start address you want to crawl. Also read the great post by Corey Roth about how to configure the rights for the user used for the crawling file shares.

    docpush is mainly used for testing, and there are only some very special production scenarios which would requires the use of docpush.

    And -g is used together with -r. By default docpush will read the contents of the file and send it to the content distributor and pipeline for processing. -r will only send a reference, and the pipeline will fetch the contents of the file.

    Example - c:\share is mapped to \\serverA\share

    docpush -c sp c:\share\myfile.doc -u file://serverA/share/

    (I haven't tested this, so it might be -u file://serverA/)

    Regards,
    Mikael Svenson 


    Search Enthusiast - MCTS SharePoint/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Proposed as answer by Barry Waldbaum Wednesday, June 8, 2011 2:57 AM
    Tuesday, June 7, 2011 8:11 PM
  • The best practice around this is to not feed test documents into the 'sp' collection.

    • create a test collection: New-FASTContentCollection -name test
    • push documents into the test collection: docpush -c test ...
    • empty out the test collection: Clear-FASTContentCollection -name test
    • remove the test collection: Remove-FASTContentCollection -name test

    This is also recommended to use a different collection for JDBC connector, FAST Web crawler, and the FAST content SDK. It's also very easy to create a scope, so the FQL would be: meta.collection:test which would only return documents from the test collection

    Wednesday, June 8, 2011 2:57 AM