tag:blogger.com,1999:blog-19503449926658443842024-03-21T07:14:26.568-07:00Siddhast labAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.comBlogger304125tag:blogger.com,1999:blog-1950344992665844384.post-52124737037363491662018-06-05T18:46:00.001-07:002018-06-05T18:46:18.441-07:00SSH – Putty Clear Cache – Compunet Blog<div dir="auto"><a href="https://blog.compunet.co.za/ssh-putty-clear-cache/">https://blog.compunet.co.za/ssh-putty-clear-cache/</a></div> Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-15438567503313549772018-05-27T21:40:00.000-07:002018-05-27T21:41:33.427-07:00some IPR question on software licenses<div dir="ltr"><div>A research project in the area of intellectual property requires software that certainly has a number of functionalities that are specific to other niche projects that the project owners envisage, such as, an atypical examination of how courts deal with copyright cases including staff training, lobbying and influence activities that they wish to study. The project team would require these functionalities for limited periods and not necessarily for long-term use. They find that funding for such time-bound and specific projects, which are very useful, to be challenging. Since the project is time-bound and would need further study there are limited time and financial resources.</div><div><br></div><div> </div><div><br></div><div>The key legal characteristics of open source software may make it a model most suitable in this context. Which of the characteristics below are NOT suitable for such a project:</div><div><br></div><div>Select one:</div><div>a. The opportunity to freely modify and improve the software;</div><div>b. The use of the software for any purpose, subject to the authorization of its creator;</div><div>c. The lack of royalties;</div><div>d. The opportunity to redistribute the software and its modified version</div><div><br></div><div>OSS is mainly a technical development model supported by standard licenses, with projects hosted online. Anyone can usually join and participate, either contributing code, documentating, offering graphics or financial support. However, it is a "development" model, not a "commercialization" model. As a result FOSS has often been seen as having purely technical advantages but also drawbacks associated to immaturity, security breaches, and technical and legal complexity.</div><div><br></div><div> </div><div><br></div><div>Which among the following technical characteristics may NOT be associated with free and open source software:</div><div><br></div><div>Select one:</div><div>a. Reliability, auditability, interoperability</div><div>b. Openness, accessibility, customizable</div><div>c. Enterprise-grade support, local sales channel, warranties</div><div>d. Open standards compatible, technology independence, security</div><div><br></div><div>Kerala International Centre for Free and Open Source Software</div><div><br></div><div>"Background: Following the State Government approval by law on the setting up of The International Centre for Free and Open Source Software (ICFOSS), the institution will be set up at Thiruvananthapuram. In a Press Meet in December 2009, the Hon'ble Chief Minister Shri.V.S.Achuthanandan, who also holds the charge for IT Department said that the Centre has been planned as part of the Government's programme to promote free software in the State.</div><div><br></div><div>In this present era that has witnessed explosion of knowledge thanks to the Internet, it is important to democratise access to knowledge. The Nobel Prize winning economist, Joseph Stiglitz theorizes that disparity over access to information and knowledge is humanity's single most potent cause of poverty and discord. This challenge to democratise knowledge has in recent years, given birth to a radical paradigm called Free and Open Source Software (FOSS), as a powerful alternative to monopolistic approaches to knowledge creations. The Kerala Government has time and again affirmed its intention to foster the State as a global destination for FOSS based software and IT enabled services.</div><div><br></div><div>ICFOSS is expected to go a long way in making Kerala a global FOSS destination. Some of the areas that this institution proposes to take up includes developing and customising Open Source applications, FOSS localization to Indian languages and speech interfaces on FOSS for the illiterate.</div><div><br></div><div>Vision and Mission: The vision of ICFOSS is to become a leading research organisation in Free and Open Source model of knowledge development thereby contributing towards sustainable development of society and to stimulate economic development in the region. The mission of ICFOSS is to promote research and development in the area of Free and Open Source Software and the knowledge development model it puts forward.</div><div><br></div><div> </div><div><br></div><div>The main objective of the ICFOSS is:</div><div><br></div><div>Select one:</div><div>a. developing and customising Open Source applications</div><div>b. to become a leading research organisation in Free and Open Source model of knowledge development</div><div>c. contributing to sustainable development of society and to stimulate economic development in the region</div><div>d. all of the above</div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:12.8px">Roshan Agarwal</span><br></div><div><span style="font-size:12.8px">Chief Executive officer</span></div><div><span style="font-size:12.8px">Siddhast Ip innovation (P) ltd</span><br></div><div>907 chandra vihar colony</div><div>Jhansi-284002<br>M:+917376314900<br></div></div></div></div></div></div></div></div> </div> Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-17177054628250396222018-04-15T15:32:00.001-07:002018-04-15T15:32:15.181-07:00Starting services in safe mode<div dir="auto"><div dir="auto"><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px">Recently I was trying to figure out how to start additional services in Windows safe mode. I had a user whose laptop kept crashing at login, I had a quick look and several theories came to mind but uptime was important, so as a temporary workaround I set it up in safe mode with networking.</p><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px">A few days later the user calls and wants to be able to print in safe mode. I look into it, do some searching, but the prevailing wisdom seemed to be that it wasn't doable. This sounded like an MCP party line to me so I decide to explore the registry. Eventually I find the<span style="width:100%;padding:0px 2px;margin:0px 2px;font-family:monaco,monacoregular,"courier new",monospace;border-width:1px!important;border-color:rgb(153,153,153)!important;border-style:solid!important;background:rgb(39,40,34)!important;direction:ltr!important;line-height:20px!important"><span style="color:rgb(0,0,0);width:100%;margin:0px;padding:0px;font-family:consolas,consolasregular,"courier new",monospace!important;background:none!important;border:none!important;line-height:20px!important"><span style="font-family:inherit;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important;color:rgb(102,217,239)!important">HKEY_LOCAL_MACHINE</span>\SYSTEM\CurrentControlSet\Control</span></span> key which has sub-keys of Minimal and Network. Minimal being safe mode, Network being safe mode with networking. It seems to be a whitelist of services, drivers and drive groups that are allowed to start or load.</p><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px">Therefore it is possible to start additional services and load additional drivers in safe mode – just add a key for the service or driver short name, then a string for type. The below entry (if in a .reg file) would allow the Print Spooler to start in safe mode with networking.</p><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px"></p><div style="width:328px;padding:0px;margin:20px 0px;font-family:monaco,monacoregular,"courier new",monospace;color:rgb(58,65,69);height:auto;border-width:1px!important;border-color:rgb(153,153,153)!important;border-style:solid!important;background:rgb(39,40,34)!important;direction:ltr!important;font-size:16px!important;line-height:20px!important" dir="auto"><div style="border-top:0px;border-right:0px;border-left:0px;padding:0px;margin:0px;width:326px;font-family:consolas,consolasregular,"courier new",monospace!important;background:rgb(221,221,221)!important;border-bottom:1px solid rgb(187,187,187)!important;height:24px!important;line-height:24px!important"><span style="font-family:inherit;color:rgb(51,51,51)!important;float:left;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important;padding:0px 4px!important"></span><div style="font-family:inherit;background:0px center;border:0px;padding:0px;margin:0px;height:24px!important;line-height:24px!important;font-weight:inherit!important;float:right!important"><div style="font-family:inherit;background-position:0px center;background-repeat:no-repeat;border:0px;padding:0px;margin:0px;height:inherit;line-height:15px;display:inline;width:24px;font-size:inherit!important;font-weight:inherit!important;float:left!important"><div style="font-family:inherit;background:0px -32px/48px 128px;border:0px;padding:0px;margin:0px;width:24px;height:16px!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important"></div></div><div style="font-family:inherit;background-position:0px center;background-repeat:no-repeat;border:0px;padding:0px;margin:0px;height:inherit;line-height:15px;display:inline;width:24px;font-size:inherit!important;font-weight:inherit!important;float:left!important"><div style="font-family:inherit;background:0px -48px/48px 128px;border:0px;padding:0px;margin:0px;width:24px;height:16px!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important"></div></div><div style="font-family:inherit;background-position:0px center;background-repeat:no-repeat;border:0px;padding:0px;margin:0px;height:inherit;line-height:15px;display:inline;width:24px;font-size:inherit!important;font-weight:inherit!important;float:left!important"><div style="font-family:inherit;background:0px -112px/48px 128px;border:0px;padding:0px;margin:0px;width:24px;height:16px!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important"></div></div><div style="font-family:inherit;background-position:0px center;background-repeat:no-repeat;border:0px;padding:0px;margin:0px;height:inherit;line-height:15px;display:inline;width:24px;font-size:inherit!important;font-weight:inherit!important;float:left!important"><div style="font-family:inherit;background:0px -96px/48px 128px;border:0px;padding:0px;margin:0px;width:24px;height:16px!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important"></div></div><div style="font-family:inherit;background-position:0px center;background-repeat:no-repeat;border:0px;padding:0px;margin:0px;height:inherit;line-height:15px;display:inline;width:24px;font-size:inherit!important;font-weight:inherit!important;float:left!important"><div style="font-family:inherit;background:0px 0px/48px 128px;border:0px;padding:0px;margin:0px;width:24px;height:16px!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important"></div></div></div></div><div style="background:0px center;border:0px;font-family:consolas,consolasregular,"courier new",monospace!important;padding:0px!important;margin:0px!important;height:auto!important"><textarea style="margin:0px;vertical-align:top;color:rgb(0,0,0);border-width:0px;border-style:initial;border-color:initial;border-radius:0px;width:326px;padding:0px 5px;height:71px;white-space:pre;word-wrap:normal;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;font-family:consolas,consolasregular,"courier new",monospace!important;font-size:16px!important;line-height:20px!important"></textarea></div><div style="background:0px center;border:0px;padding:0px;margin:0px;width:326px;font-family:consolas,consolasregular,"courier new",monospace!important"><table style="max-width:100%;font-size:12px;border-spacing:0px!important;border-collapse:collapse!important;width:auto!important;margin-top:0px!important;margin-right:0px!important;margin-bottom:0px!important;background:none!important;border:none!important;padding:0px!important;table-layout:auto!important"><tbody><tr style="background:0px center;padding:0px!important;border:none!important;vertical-align:top!important;margin:0px!important"><td style="line-height:20px;border:0px;padding:0px!important;vertical-align:top!important;margin:0px!important;background-image:initial!important;background-position:initial!important;background-size:initial!important;background-repeat:initial!important;background-origin:initial!important;background-clip:initial!important;color:rgb(134,134,134)!important"><div style="background:0px center;border:0px;padding:0px;margin:0px;white-space:nowrap;font-size:16px!important;line-height:20px!important"><div style="font-family:inherit;background:0px center;border:0px;padding:0px 5px;margin:0px;text-align:center;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important">1</div><div style="font-family:inherit;border:0px;padding:0px 5px;margin:0px;text-align:center;height:inherit;background:rgb(50,50,42)!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important">2</div></div></td><td style="line-height:20px;border:0px;background:0px center;width:697px;padding:0px!important;vertical-align:top!important;margin:0px!important"><div style="padding:0px;margin:0px;color:rgb(0,0,0);white-space:pre;background:none!important;border:none!important;font-size:16px!important;line-height:20px!important"><div style="font-family:inherit;background:0px center;border:0px;padding:0px 5px;margin:0px;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important">[<span style="font-family:inherit;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important;color:rgb(102,217,239)!important">HKEY_LOCAL_MACHINE</span>\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\Spooler]</div><div style="font-family:inherit;border:0px;padding:0px 5px;margin:0px;height:inherit;background-image:initial!important;background-position:initial!important;background-size:initial!important;background-repeat:initial!important;background-origin:initial!important;background-clip:initial!important;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important"><span style="font-family:inherit;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important">@</span>=<span style="font-family:inherit;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important;color:rgb(230,219,93)!important">"Service"</span></div></div></td></tr></tbody></table></div></div><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px"></p><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px">If you want a list of all drivers, driver groups and services starting in normal mode and their corresponding short names check<span style="width:100%;padding:0px 2px;margin:0px 2px;font-family:monaco,monacoregular,"courier new",monospace;border-width:1px!important;border-color:rgb(153,153,153)!important;border-style:solid!important;background:rgb(39,40,34)!important;direction:ltr!important;line-height:20px!important"><span style="color:rgb(0,0,0);width:100%;margin:0px;padding:0px;font-family:consolas,consolasregular,"courier new",monospace!important;background:none!important;border:none!important;line-height:20px!important"><span style="font-family:inherit;height:inherit;font-size:inherit!important;line-height:inherit!important;font-weight:inherit!important;color:rgb(102,217,239)!important">HKEY_LOCAL_MACHINE</span>\SYSTEM\CurrentControlSet\Services</span></span></p><p style="margin:1.6em 0px;color:rgb(58,65,69);font-family:"noto serif",serif;font-size:16px">I'd caution against whitelisting too much as it kind of defeats the purpose of safe mode, though in certain situations as a quick hack it can useful. It may also be something worth checking the next time you're dealing with a particularly nasty malware infection. I haven't seen anything which exploits it yet, but I imagine something does.</p></div><div dir="auto"><br></div><div dir="auto"><br></div><a href="http://www.krisdavidson.org/2010/09/11/starting-services-in-safe-mode/">http://www.krisdavidson.org/2010/09/11/starting-services-in-safe-mode/</a></div> Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-46808327392794035292018-04-12T23:41:00.001-07:002018-04-12T23:41:11.333-07:00FW: ZKPropertiesWriter error DIH (SolrCloud 6.6.1)-----Original Message-----
<br>From: msaunier [mailto:<a href="mailto:msaunier@citya.com">msaunier@citya.com</a>]
<br>Sent: 09 April 2018 13:49
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: RE: ZKPropertiesWriter error DIH (SolrCloud 6.6.1)
<br>
<br>I up my subject. Thanks
<br>
<br>
<br>
<br>
<br>
<br>-----Message d'origine-----
<br>De : msaunier [mailto:<a href="mailto:msaunier@citya.com">msaunier@citya.com</a>] Envoyé : jeudi 5 avril 2018 10:46
<br>À : <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a> Objet : RE: ZKPropertiesWriter error DIH
<br>(SolrCloud 6.6.1)
<br>
<br>I have use this process to create the DIH :
<br>
<br>1. Create the BLOB collection:
<br> * curl
<br><a href="http://localhost:8983/solr/admin/collections?action=CREATE&name=.system">http://localhost:8983/solr/admin/collections?action=CREATE&name=.system</a>
<br>
<br>2. Send definition and file for DIH
<br> * curl -X POST -H 'Content-Type: application/octet-stream' --data-binary
<br>@ solr-dataimporthandler-6.6.1.jar
<br><a href="http://localhost:8983/solr/.system/blob/DataImportHandler">http://localhost:8983/solr/.system/blob/DataImportHandler</a>
<br> * curl -X POST -H 'Content-Type: application/octet-stream' --data-binary
<br>@ mysql-connector-java-5.1.46.jar
<br><a href="http://localhost:8983/solr/.system/blob/MySQLConnector">http://localhost:8983/solr/.system/blob/MySQLConnector</a>
<br> * curl <a href="http://localhost:8983/solr/advertisements2/config">http://localhost:8983/solr/advertisements2/config</a> -H
<br>'Content-type:application/json' -d '{"add-runtimelib": {
<br>"name":"DataImportHandler", "version":1 }}'
<br> * curl <a href="http://localhost:8983/solr/advertisements2/config">http://localhost:8983/solr/advertisements2/config</a> -H
<br>'Content-type:application/json' -d '{"add-runtimelib": {
<br>"name":"MySQLConnector", "version":1 }}'
<br>
<br>3. I have add on the config file the requestHandler with the API. Result :
<br>###
<br> "/full-advertisements": {
<br> "runtimeLib": true,
<br> "version": 1,
<br> "class": "org.apache.solr.handler.dataimport.DataImportHandler",
<br> "defaults": {
<br> "config": "DIH/advertisements.xml"
<br> },
<br> "name": "/full-advertisements"
<br> },
<br>###
<br>
<br>4. I have add with the zkcli.sh script the .xml definition file in
<br>/configs/advertisements2/DIH/advertisements.xml
<br>###
<br> <dataConfig>
<br>
<br> <dataSource name="Gesloc" type="JdbcDataSource"
<br>driver="com.mysql.jdbc.Driver"
<br>url="jdbc:mysql://srv-gesloc-sql/TRANSACTIONCITYANEWLOCATION" user="ics"
<br>password="******" />
<br>
<br> <document>
<br>
<br> <entity name="Advertisements_Gesloc" dataSource="Gesloc" pk="id"
<br>transformer="TemplateTransformer" query="SELECT id,origin FROM
<br>view_indexation_advertisements" >
<br>
<br> <field column="id" name="id"/>
<br> <field column="origin" name="origin"/>
<br>
<br> </entity>
<br>
<br> </document>
<br>
<br> </dataConfig>
<br>###
<br>
<br>Thanks for your help.
<br>
<br>
<br>-----Message d'origine-----
<br>De : msaunier [mailto:<a href="mailto:msaunier@citya.com">msaunier@citya.com</a>] Envoyé : mercredi 4 avril 2018
<br>09:57 À : <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a> Cc : <a href="mailto:fharrang@citya.com">fharrang@citya.com</a> Objet :
<br>ZKPropertiesWriter error DIH (SolrCloud 6.6.1)
<br>
<br>Hello,
<br>I use Solr Cloud and I test DIH system in cloud, but I have this error :
<br>
<br>Full Import
<br>failed:org.apache.solr.handler.dataimport.DataImportHandlerException: Unable
<br>to PropertyWriter implementation:ZKPropertiesWriter at
<br>org.apache.solr.handler.dataimport.DataImporter.createPropertyWriter(DataImp
<br>orter.java:330)
<br>at
<br>org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.ja
<br>va:411)
<br>at
<br>org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:474
<br>)
<br>at
<br>org.apache.solr.handler.dataimport.DataImporter.lambda$runAsync$0(DataImport
<br>er.java:457)
<br>at java.lang.Thread.run(Thread.java:748)
<br>Caused by: java.lang.NullPointerException at
<br>org.apache.solr.handler.dataimport.DocBuilder.loadClass(DocBuilder.java:935)
<br>at
<br>org.apache.solr.handler.dataimport.DataImporter.createPropertyWriter(DataImp
<br>orter.java:326)
<br>... 4 more
<br>
<br>My DIH definition on the cloud
<br>
<br><dataConfig>
<br>
<br><dataSource name="Gesloc" type="JdbcDataSource"
<br>driver="com.mysql.jdbc.Driver"
<br>url="jdbc:mysql://srv-gesloc-sql/TRANSACTIONCITYANEWLOCATION" user="ics"
<br>password="IcsPerms"
<br>runtimeLib="true" version="1"/>
<br>
<br><document>
<br>
<br><entity name="Advertisements_Gesloc" dataSource="Gesloc" pk="id"
<br>transformer="TemplateTransformer"
<br>query="SELECT id,origin FROM view_indexation_advertisements" >
<br>
<br><field column="id" name="id"/>
<br><field column="origin" name="origin"/>
<br>
<br></entity>
<br>
<br></document>
<br>
<br></dataConfig>
<br>
<br>Call response :
<br>
<br><<a href="http://localhost:8983/solr/advertisements2/full-advertisements?command=full-import&clean=false&commit=true">http://localhost:8983/solr/advertisements2/full-advertisements?command=full
<br>-import&clean=false&commit=true</a>>
<br><a href="http://localhost:8983/solr/advertisements2/full-advertisements?command=full-import&clean=false&commit=true">http://localhost:8983/solr/advertisements2/full-advertisements?command=full-
<br>import&clean=false&commit=true</a>
<br>
<br><response>
<br><lst name="responseHeader">
<br><int name="status">0</int>
<br><int name="QTime">2</int>
<br></lst>
<br><lst name="initArgs">
<br><bool name="runtimeLib">true</bool>
<br><long name="version">1</long>
<br><lst name="defaults">
<br><str name="config">DIH/advertisements.xml</str>
<br></lst>
<br></lst>
<br><str name="command">full-import</str>
<br><str name="status">idle</str>
<br><str name="importResponse"/>
<br><lst name="statusMessages"/>
<br></response>
<br>
<br>I don't understand why I have this error. Can you help me ?
<br>Thanks you.Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-81657841669441276092018-04-09T03:46:00.005-07:002018-04-09T03:46:33.022-07:00FW: Default Index config-----Original Message-----
<br>From: mganeshs [mailto:<a href="mailto:mganeshs@live.in">mganeshs@live.in</a>]
<br>Sent: 09 April 2018 15:34
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Default Index config
<br>
<br>Hi Shawn,
<br>
<br>Regarding CPU high, when we are troubleshooting, we found that Merge threads
<br>are keep on running and it's take most CPU time ( as per Visual JVM ). GC is
<br>not causing any issue as we use the default GC and also tried with G1 as you
<br>suggested over here
<br><<a href="https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning_for_Solr">https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning_for_Solr</a>>
<br>
<br>Though it's only background process, we are suspecting whether it's causing
<br>CPU to go high.
<br>
<br>Since we are using SOLR as real time indexing of data and depending on its
<br>result immd. to show it in UI as well. So we keep adding document around 100
<br>to 200 documents in parallel in a sec. Also it would be in batch of 20 solr
<br>documents list in one add...
<br>
<br>*Note*: following is the code snippet we use for indexing / adding solr
<br>document in batch per collection
<br>
<br>/for (SolrCollectionList solrCollection : SolrCollectionList.values()) {
<br> CollectionBucket collectionBucket =
<br>getCollectionBucket(solrCollection);
<br> List<SolrInputDocument> solrInputDocuments =
<br>collectionBucket.getSolrInputDocumentList();
<br> String collectionName = collectionBucket.getCollectionName();
<br> try {
<br> if(solrInputDocuments.size() > 0) {
<br> CloudSolrClient solrClient =
<br>PlatformIndexManager.getInstance().getCloudSolrClient(collectionName);
<br> solrClient.add(collectionName, solrInputDocuments);
<br> }
<br>}/
<br>
<br>*where solrClient is created as below
<br>*
<br>/this.cloudSolrClient = new
<br>CloudSolrClient.Builder().withZkHost(zooKeeperHost).withHttpClient(HttpClien
<br>tUtil.HttpClientFactory.createHttpClient()).build();
<br>this.cloudSolrClient.setZkClientTimeout(30000);
<br>/
<br>
<br>Hard commit is kept as automatic and set to 15000 ms.
<br>In this process, we also see, when merge is happening, and already
<br>maxMergeCount ( default one ) is reached, commits are getting delayed and
<br>solrj client ( where we add document ) is getting blocked and once once of
<br>Merge thread process the merge, then solrj client returns the result.
<br>How do we avoid this blocking of solrj client ? Do I need to go out of
<br>default config for this scenario? I mean change the merge factor
<br>configuration ?
<br>
<br>Can you suggest what would be merge config for such a scenario ? Based on
<br>forums, I tried to change the merge settings to the following,
<br>
<br><mergePolicyFactory class="org.apache.solr.index.TieredMergePolicyFactory">
<br> <int name="maxMergeAtOnce">30</int>
<br> <int name="maxMergeAtOnceExplicit">30</int>
<br> <int name="segmentsPerTier">30</int>
<br> <int name="floorSegmentMB">2048</int>
<br> <int name="maxMergedSegmentMB">512</int>
<br> <double name="noCFSRatio">0.1</double>
<br> <int name="maxCFSSegmentSizeMB">2048</int>
<br> <double name="reclaimDeletesWeight">2.0</double>
<br> <double name="forceMergeDeletesPctAllowed">10.0</double>
<br></mergePolicyFactory>
<br>
<br>But couldn't see any much change in the behaviour.
<br>
<br>In same solr node, we have multiple index / collection. In that case,
<br>whether TieredMergePolicyFactory will be right option or for multiple
<br>collection in same node we should go for other merge policy ( like LogByte
<br>etc )
<br>
<br>
<br>Can you throw some light on this aspects ?
<br>Regards,
<br>
<br> Regarding auto commit, we discussed lot with our product owners and atlast
<br>> we are forced to keep it to 1sec and we couldn't increase further. As
<br>> this itself, sometimes our customers says that they have to refresh
<br>> their pages for couple of times to get the update from solr. So we
<br>> can't increase further.
<br>
<br>I understand pressure from nontechnical departments for very low response
<br>times. Executives, sales, and marketing are usually the ones making those
<br>kinds of demands. I think you should push back on that particular
<br>requirement on technical grounds.
<br>
<br>A soft commit interval that low *can* contribute to performance issues. It
<br>doesn't always cause them, I'm just saying that it *can*.  Maybe increasing
<br>it to five or ten seconds could help performance, or maybe it will make no
<br>real difference at all.
<br>
<br>> Yes. As of now only solr is running in that machine. But intially we
<br>> were running along with hbase region servers and was working fine. But
<br>> due to CPU spikes and OS disk cache, we are forced to move solr to
<br>> separate machine.
<br>> But just I checked, our solr data folder size is coming only to 17GB.
<br>> 2 collection has around 5GB and other are have 2 to 3 GB of size. If
<br>> you say that only 2/3 of total size comes to OS disk cache, in top
<br>> command VIRT property it's always 28G, which means more than what we
<br>> have. Why is that...
<br>> Pls check that top command & GC we used in this doc
<br>> &lt;<a href="https://docs.google.com/document/d/1SaKPbGAKEPP8bSbdvfX52gaLsYWnQf">https://docs.google.com/document/d/1SaKPbGAKEPP8bSbdvfX52gaLsYWnQf</a>
<br>> DqfmV802hWIiQ/edit?usp=sharing&gt;
<br>
<br>The VIRT memory should be about equivalent to the RES size plus the size of
<br>all the index data on the system.  So that looks about right.  The actual
<br>amount of memory allocated by Java for the heap and other memory structures
<br>is approximately equal to RES minus SHR.
<br>
<br>I am not sure whether the SHR size gets counted in VIRT. It probably does. 
<br>On some Linux systems, SHR grows to a very high number, but when that
<br>happens, it typically doesn't reflect actual memory usage.  I do not know
<br>why this sometimes happens.That is a question for Oracle, since they are the
<br>current owners of Java.
<br>
<br>Only 5GB is in the buff/cache area.  The system has 13GB of free memory. 
<br>That system is NOT low on memory.
<br>
<br>With 4 CPUs, a load average in the 3-4 range is an indication that the
<br>server is busy.  I can't say for sure whether it means the server is
<br>overloaded.  Sometimes the load average on a system that's working well can
<br>go higher than the CPU count, sometimes a load average well below the CPU
<br>count is shown on a system with major performance issues.  It's difficult to
<br>say.  The instantaneous CPU usage on the Solr process in that screenshot is
<br>384 percent.  Which means that it is exercising the CPUs hard. But this
<br>might be perfectly OK.  96.3 percent of the CPU is being used by user
<br>processes, a VERY small amount is being used by system, and the iowait
<br>percentage is zero.  Typically servers that are struggling will have a
<br>higher percentage in system and/or iowait, and I don't see that here.
<br>
<br>> Queries are quiet fast, most of time simple queries with fq. Regarding
<br>> index, during peak hours, we index around 100 documents in a second in
<br>> a average.
<br>
<br>That's good.  And not surprising, given how little memory pressure and how
<br>much free memory there is.  An indexing rate of 100 per second doesn't seem
<br>like a lot of indexing to me, but for some indexes, it might be very heavy. 
<br>If your general performance is good, I wouldn't be too concerned about it.
<br>
<br>> Regarding release, initially we tried with 6.4.1 and since many
<br>> discussions over here, mentioned like moving to 6.5.x will solve lot
<br>> of performance issues etc, so we moved to 6.5.1. We will move to 6.6.3
<br>> in near future.
<br>
<br>The 6.4.1 version had a really bad bug in it that killed performance for
<br>most users.  Some might not have even noticed a problem, though.  It's
<br>difficult to say for sure whether it would be something you would notice, or
<br>whether you would see an increase in performance by upgrading.
<br>
<br>> Hope I have given enough information. One strange thing is that, CPU
<br>> and memory spike are not seen when we move to r4.xlarge to r4.2xlarge
<br>> ( which is
<br>> 8 core with 60 GB RAM ). But this would not be cost effective. What's
<br>> making CPU and memory to go high in this new version ( due to doc
<br>> values )? If I switch off docvalues will CPU & Memory spikes will get
<br>> reduced ?
<br>
<br>Overall memory usage (outside of the Java heap) looks great to me.  CPU
<br>usage is high, but I can't tell if it's TOO high. As a proof of concept, I
<br>think you should try raising autoSoftCommit to five seconds.  If maxDocs is
<br>configured on either autoCommit or autoSoftCommit, remove it so that only
<br>maxTime is there, regardless of whether you actually change maxTime.  If
<br>raising autoSoftCommit makes no real difference, then the 1 second
<br>autoSoftCommit probably isn't a worry.  I bet if you raised it to five
<br>seconds, most users would never notice anything different.
<br>
<br>If you want to provide a GC log to us that covers a relatively long
<br>timeframe, we can analyze that and let you know whether your heap is sized
<br>appropriately, or whether it might be too big or too small, and whether
<br>garbage collection pauses are keeping your CPU usage high.  The standard
<br>Solr startup in most current versions always logs GC activity. It will
<br>usually be in the same directory as solr.log.
<br>
<br>Do you know what typical and peak queries per second are on your Solr
<br>servers?  If your query rate is high, handling that will probably require
<br>more servers and a higher replica count.
<br>
<br>Thanks,
<br>Shawn
<br>
<br>
<br>
<br>
<br>
<br>--
<br>Sent from: <a href="http://lucene.472066.n3.nabble.com/Solr-User-f472068.html">http://lucene.472066.n3.nabble.com/Solr-User-f472068.html</a>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-3289690898017246282018-04-09T03:46:00.003-07:002018-04-09T03:46:31.007-07:00FW: Match a phrase like "Apple iPhone 6 32GB white" with "iphone 6"-----Original Message-----
<br>From: Alessandro Benedetti [mailto:<a href="mailto:a.benedetti@sease.io">a.benedetti@sease.io</a>]
<br>Sent: 09 April 2018 15:43
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Match a phrase like "Apple iPhone 6 32GB white" with "iphone 6"
<br>
<br>Hi Sami,
<br>I agree with Mikhail, if you have relatively complex data you could curate
<br>your own knowledge base for products as use it for Named entity Recognition.
<br>You can then search a field compatible_with the extracted entity.
<br>
<br>If the scenario is simpler using the analysis chain you mentioned should
<br>work (if the product names are always complete and well curated).
<br>
<br>Cheers
<br>
<br>
<br>
<br>
<br>
<br>--------------------------
<br>Alessandro Benedetti
<br>Search Consultant, R&D Software Engineer, Director <a href="http://www.sease.io">www.sease.io</a>
<br>
<br>On Mon, Apr 9, 2018 at 10:40 AM, Adhyan Arizki <<a href="mailto:a.arizki@gmail.com">a.arizki@gmail.com</a>> wrote:
<br>
<br>> You can just use synonyms for that.. rather hackish but it works
<br>>
<br>> On Mon, 9 Apr 2018, 05:06 Sami al Subhi, <<a href="mailto:sami@alsubhi.me">sami@alsubhi.me</a>> wrote:
<br>>
<br>> > I think this filter will output the desired result:
<br>> >
<br>> > <analyzer type="query">
<br>> > <tokenizer class="solr.StandardTokenizerFactory"/>
<br>> > <filter class="solr.LowerCaseFilterFactory"/>
<br>> > <filter class="solr.ShingleFilterFactory"/>
<br>> > </analyzer>
<br>> > <analyzer type="index">
<br>> > <tokenizer class="solr.StandardTokenizerFactory"/>
<br>> > <filter class="solr.LowerCaseFilterFactory"/>
<br>> > <filter class="solr.FingerprintFilterFactory" separator=" " />
<br>> > </analyzer>
<br>> >
<br>> > indexing:
<br>> > "iPhone 6" will be indexed as "iphone 6" (always a single token)
<br>> >
<br>> > querying:
<br>> > so this will analyze "Apple iPhone 6 32GB white" to "apple", "apple
<br>> > iphone", "iphone", "iphone 6" and so on...
<br>> > then here a match will be achieved using the 4th token.
<br>> >
<br>> >
<br>> > I dont see how this will result in false positive matching.
<br>> >
<br>> >
<br>> >
<br>> >
<br>> > --
<br>> > Sent from: <a href="http://lucene.472066.n3.nabble.com/Solr-User-f472068.html">http://lucene.472066.n3.nabble.com/Solr-User-f472068.html</a>
<br>> >
<br>>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-42681438218766913262018-04-09T03:46:00.001-07:002018-04-09T03:46:28.114-07:00FW: Solr join With must clause in fq-----Original Message-----
<br>From: Mikhail Khludnev [mailto:<a href="mailto:mkhl@apache.org">mkhl@apache.org</a>]
<br>Sent: 09 April 2018 15:49
<br>To: solr-user <<a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>>
<br>Subject: Re: Solr join With must clause in fq
<br>
<br>it might make sense to test on the recent versions of Solr.
<br>
<br>On Sun, Apr 8, 2018 at 8:21 PM, manuj singh <<a href="mailto:s.manuj545@gmail.com">s.manuj545@gmail.com</a>> wrote:
<br>
<br>> Hi all,
<br>> I am trying to debug a problem which i am facing and need some help.
<br>>
<br>> I have a solr query which does join on 2 different cores. so lets say
<br>> my first core has following 3 docs
<br>>
<br>> { "id":"1", "m_id":"lebron", "some_info":"29" }
<br>>
<br>> { "id":"2", "m_id":"Wade", "matches_win":"29" }
<br>>
<br>> { "id":"3", "m_id":"lebron", "some_info":"1234" }
<br>>
<br>> my second core has the following docs
<br>>
<br>> { "m_id": "lebron", "team": "miami" }
<br>>
<br>> { "m_id": "Wade", "team": "miami" }
<br>>
<br>> so now we made an update to doc with lebron and changed the team to
<br>> "clevelend". So the new docs in core 2 looks like this.
<br>>
<br>> { "m_id": "lebron", "team": "clevelend" }
<br>>
<br>> { "m_id": "Wade", "team": "miami" }
<br>>
<br>> now i am trying to join these 2 and finding the docs form core1 for
<br>> team miami.
<br>>
<br>> my query looks like this
<br>>
<br>> fq=+{!join from=m_id to=m_id fromIndex=core2 force=true}team:miami
<br>>
<br>> I am expecting it to return doc with id=2 but what i am getting is
<br>> document
<br>> 1 and 2.
<br>>
<br>> I am not able to figure out what is the problem. Is the query incorrect ?
<br>> or is there some issue in join.
<br>>
<br>> *Couple of observations.*
<br>>
<br>> 1.if i remove the + from the filter query it works as expected. so the
<br>> following query works
<br>>
<br>> fq={!join from=m_id to=m_id fromIndex=core2 force=true}team:miami
<br>>
<br>> I am not sure how the Must clause affecting the query.
<br>>
<br>> *2.* Also if you look the original query is not returning document
<br>> 3.(however its returning document 1 which has the same m_id). Now the
<br>> only difference between doc 1 and doc3 is that doc1 was created when
<br>"lebron"
<br>> was part of team: miami. and doc3 was created when the team got
<br>> updated to "cleveland". So the join is working fine for the new docs
<br>> in core1 but not for the old docs.
<br>>
<br>> 3.If i use q instead of fq the query returns results as expected.
<br>>
<br>> q=+{!join from=m_id to=m_id fromIndex=core2 force=true}team:miami
<br>>
<br>> and
<br>>
<br>> q={!join from=m_id to=m_id fromIndex=core2 force=true}team:miami
<br>>
<br>> Both of the above works.
<br>>
<br>> I am sure i am missing something how internally join works. I am
<br>> trying to understand why fq has a different behavior then q with the
<br>Must(+) clause.
<br>>
<br>> I am using solr 4.10.
<br>>
<br>>
<br>>
<br>> Thanks
<br>>
<br>> Manuj
<br>>
<br>
<br>
<br>
<br>--
<br>Sincerely yours
<br>Mikhail KhludnevAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-40055691824173311132018-04-02T02:38:00.001-07:002018-04-02T02:38:33.763-07:00FW: custom filter class on schema.xml on solrcloud-----Original Message-----
<br>From: void [mailto:<a href="mailto:sauravsust71@gmail.com">sauravsust71@gmail.com</a>]
<br>Sent: 02 April 2018 14:32
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: custom filter class on schema.xml on solrcloud
<br>
<br>I have used a custom filter provided by a jar in schema.xml in standalone
<br>Solr like below
<br>
<br><filter class="com.x.yFilterFactory"
<br>stopWordDictionary="resources/yStopWords"/>
<br>
<br>And for this,
<br>
<br>I have loaded the jar in solrconfig.xml like below
<br>
<br><lib dir="./../plugins/" regex=".*\.jar" />
<br>
<br>It's working fine But when I've tried to use it in solrcloud with external
<br>zookeeper mode I've got an error 'IO exception' maybe for uploading a large
<br>jar file in zookeeper.
<br>
<br>I've also tried to put this jar in the lib folder of solr home but got error
<br>'Plugin init failure'
<br>
<br>After that, I've tried blob store api but the documentation says "Blob store
<br>can only be used to dynamically load components configured in
<br>solrconfig.xml. Components specified in schema.xml cannot be loaded from
<br>blob store"
<br>
<br>So, how can I use custom filter class in schema.xml in solrcloud mode with
<br>external zookeeper configuration
<br>
<br>
<br>
<br>
<br>
<br>
<br>--
<br>Sent from: <a href="http://lucene.472066.n3.nabble.com/Solr-User-f472068.html">http://lucene.472066.n3.nabble.com/Solr-User-f472068.html</a>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-63060080683556495512018-04-02T00:07:00.001-07:002018-04-02T00:07:37.886-07:00FW: Learning to Rank (LTR) with grouping-----Original Message-----
<br>From: ilayaraja [mailto:<a href="mailto:ilay.msp@gmail.com">ilay.msp@gmail.com</a>]
<br>Sent: 02 April 2018 12:27
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Learning to Rank (LTR) with grouping
<br>
<br>Hi Roopa & Deigo,
<br>
<br> I am facing same issue with grouping. Currently, am on Solr 7.2.1 but still
<br>see that grouping with LTR is not working. Did you apply it as patch or the
<br>latest solr version has the fix already?
<br>
<br>Ilay
<br>
<br>
<br>
<br>-----
<br>--Ilay
<br>--
<br>Sent from: <a href="http://lucene.472066.n3.nabble.com/Solr-User-f472068.html">http://lucene.472066.n3.nabble.com/Solr-User-f472068.html</a>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-55023718528823266962018-04-01T22:50:00.020-07:002018-04-02T11:46:25.186-07:00FW: Upgrading a Plugin from 6.6 to 7.x-----Original Message-----
<br>From: Peter Alexander Kopciak [mailto:<a href="mailto:peter@kopciak.at">peter@kopciak.at</a>]
<br>Sent: 21 March 2018 16:17
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Upgrading a Plugin from 6.6 to 7.x
<br>
<br>Hi!
<br>
<br>I'm still pretty new to Solr and I want to use the vector Scoring plugin (
<br><a href="https://github.com/saaay71/solr-vector-scoring/network">https://github.com/saaay71/solr-vector-scoring/network</a>) but unfortunately,
<br>it does not seem to work for newer Solr versions.
<br>
<br>I tested it with 6.6 to verify its functionality, so it seems to be broken
<br>because of the upgrade to 7.x.
<br>
<br>When following the installation procedure and executing the examples, I ran
<br>into the following error with Query 1:
<br>
<br>java.lang.UnsupportedOperationException: Query {! type=vp f=vector
<br>vector=0.1,4.75,0.3,1.2,0.7,4.0 v=} does not implement createWeight
<br>
<br>Does anyone has a lead for me how to fix/upgrade the plugin? The
<br>createWeight method seems to exist, so I'm not sure where to start and waht
<br>the problem seems to be.Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-50238084077324650062018-04-01T22:50:00.019-07:002018-04-01T22:52:39.072-07:00FW: Get terms in solr not working-----Original Message-----
<br>From: adam rag [mailto:<a href="mailto:adamrag16@gmail.com">adamrag16@gmail.com</a>]
<br>Sent: 21 March 2018 11:10
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Get terms in solr not working
<br>
<br>To get top words in my Apache Solr instance, I am using "terms" query. When
<br>I try it to get 10 terms in 100 million of data, the data are fetching after
<br>a few minutes, But if the data is 300 million the Solr is not responding. My
<br>server memory is 100 GB.Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-15853716714882833112018-04-01T22:50:00.018-07:002018-04-01T22:51:37.403-07:00FW: solrj question-----Original Message-----
<br>From: Shawn Heisey [mailto:<a href="mailto:apache@elyograg.org">apache@elyograg.org</a>]
<br>Sent: 26 March 2018 23:06
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: solrj question
<br>
<br>On 3/26/2018 11:19 AM, Webster Homer wrote:
<br>> You may say that the String in the constructor is "meant to be query
<br>> syntax", nothing in the Javadoc says anything about the expected syntax.
<br>> Since there is also a method to set the query, it seemed reasonable to
<br>> expect that it would take the output of the toString method. (or some
<br>> other serialization method)
<br>
<br>You're right that the javadoc is not very specific.  It says this:
<br>
<br>Parameters:
<br>    q - query string
<br>
<br>In general in Solr, "query string" is understood to be something you would
<br>put in the "q" parameter when you send a query.  Or maybe the "fq"
<br>parameter.  The javadoc could definitely be improved.
<br>
<br>The javadoc for the toString specifically used here is a little more
<br>specific.  (SolrQuery inherits from SolrParams, and that's where the
<br>toString method is defined):
<br>
<br><a href="https://lucene.apache.org/solr/6_6_0/solr-solrj/org/apache/solr/common/params/SolrParams.html#toString--">https://lucene.apache.org/solr/6_6_0/solr-solrj/org/apache/solr/common/param
<br>s/SolrParams.html#toString--</a>
<br>
<br>It says "so that the URL may be unambiguously pasted back into a browser."
<br>
<br>> So how would a user play back logged queries? This seems like an
<br>> important use case. I can parse the toString output, It seems like the
<br>> constructor should be able to take it.
<br>> If not a constructor and toString, methods, I don't see methods to
<br>> serialize and deserialize the query Being able to write the complete
<br>> query to a log is important, but we also want to be able to read the
<br>> log and submit the query to solr. Being able to playback the logs
<br>> allows us to trouble shoot search issues on our site. It also
<br>> provides a way to create load tests.
<br>>
<br>> Yes I can and am going to create this functionality, it's not that
<br>> complicated, but I don't think it's unreasonable to think that the
<br>> existing API should handle it.
<br>
<br>Yes, that would be great capability to have.  But it hasn't been written
<br>yet.  A method like "parseUrlString" on SolrQuery would be a good thing to
<br>have.
<br>
<br>Thanks,
<br>ShawnAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-81881817707163545802018-04-01T22:50:00.017-07:002018-04-01T22:51:35.178-07:00FW: Default Index config-----Original Message-----
<br>From: mganeshs [mailto:<a href="mailto:mganeshs@live.in">mganeshs@live.in</a>]
<br>Sent: 26 March 2018 22:15
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Default Index config
<br>
<br>Hi,
<br>
<br>I haven't changed the solr config wrt index config, which means it's all
<br>commented in the solrconfig.xml.
<br>
<br>It's something like what I pasted before. But I would like to know whats the
<br>default value of each of this.
<br>
<br>Coz.. after loading to 6.5.1 and our document size also crossed 5GB in each
<br>of our collection. Now update of document is taking time. So would like to
<br>know whether we need to change any default configurations.
<br>
<br><indexConfig>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br> <lockType>${solr.lock.type:native}</lockType>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br> </indexConfig>
<br>
<br>
<br>
<br>
<br>Advice...
<br>
<br>
<br>
<br>--
<br>Sent from: <a href="http://lucene.472066.n3.nabble.com/Solr-User-f472068.html">http://lucene.472066.n3.nabble.com/Solr-User-f472068.html</a>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-5786506930427148622018-04-01T22:50:00.016-07:002018-04-01T22:51:34.184-07:00FW: querying vs. highlighting: complete freedom?-----Original Message-----
<br>From: Erick Erickson [mailto:<a href="mailto:erickerickson@gmail.com">erickerickson@gmail.com</a>]
<br>Sent: 26 March 2018 22:05
<br>To: solr-user <<a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>>
<br>Subject: Re: querying vs. highlighting: complete freedom?
<br>
<br>Arturas:
<br>
<br>Thanks for the "atta boy's", but I have to confess I poked a developer's
<br>list and the person (David Smiley) who, you know, like understands the
<br>highlighting code replied, and I passed it on ;
<br>
<br>I have great respect for the SO forum, but don't post to it since there's
<br>only so much time in a day, so please feel free to put that explanation over
<br>there.
<br>
<br>As for the rest, I'll have to pass today, the aforementioned time
<br>constraints are calling....
<br>
<br>Best,
<br>Erick
<br>
<br>On Mon, Mar 26, 2018 at 12:12 AM, Arturas Mazeika <<a href="mailto:mazeika@gmail.com">mazeika@gmail.com</a>> wrote:
<br>> Hi Erick,
<br>>
<br>> Adding a field-qualify to the hl.q parameter solved the issue. My
<br>> excitement is steaming over the roof! What a thorough answer: the
<br>> explanation about the behavior of solr, how it tries to interpret what
<br>> I mean when I supply a keyword without the field-qualifier. Very
<br>impressive.
<br>> Would you care (re)posting this answer to stackoverflow? If that is
<br>> too much of a hassle, I'll do this in a couple of days myself on your
<br>behalf.
<br>>
<br>> I am impressed how well, thorough, fast and fully the question was
<br>answered.
<br>>
<br>> Steven hint pushed me into this direction further: he suggested to use
<br>> the query part of solr to filter and sort out the relevant answers in
<br>> the 1st step and in the 2nd step he'd highlight all the keywords using
<br>> CTR+F (in the browser or some alternative viewer). This brought be to
<br>> the next
<br>> question:
<br>>
<br>> How can one match query terms with the analyze-chained documents in an
<br>> efficient and distributed manner? My current understanding how to
<br>> achieve this is the following:
<br>>
<br>> 1. Get the list of ids (contents) of the documents that match the
<br>> query 2. Use the <a href="http://localhost:8983/solr/#/trans/analysis">http://localhost:8983/solr/#/trans/analysis</a> to
<br>> re-analyze the document and the query 3. Use the matching of the
<br>> substrings from the original text to last filter/tokenizer/analyzer in
<br>> the analyze-chain to map the terms of the query 4. Emulate CTRL+F
<br>> highlighting
<br>>
<br>> Web Interface of Solr offers quite a bit to advance towards this goal.
<br>> If one fires this request:
<br>>
<br>> * analysis.fieldvalue=Albert Einstein (14 March 1879 – 18 April 1955)
<br>> was a German-born theoretical physicist[5] who developed the theory of
<br>> relativity, one of the two pillars of modern physics (alongside
<br>> quantum mechanics).&
<br>> * analysis.query=reletivity theory
<br>>
<br>> to one of the cores of solr, one gets the steps 1-3 done:
<br>>
<br>> <a href="http://localhost:8983/solr/trans_shard1_replica_n1/analysis/field?wt=x">http://localhost:8983/solr/trans_shard1_replica_n1/analysis/field?wt=x</a>
<br>> ml&analysis.showmatch=true&analysis.fieldvalue=Albert%20Einstein%20(14
<br>> %20March%201879%20%E2%80%93%2018%20April%201955)%20was%20a%20German-bo
<br>> rn%20theoretical%20physicist[5]%20who%20developed%20the%20theory%20of%
<br>> 20relativity,%20one%20of%20the%20two%20pillars%20of%20modern%20physics
<br>> %20(alongside%20quantum%20mechanics).&analysis.query=reletivity%20theo
<br>> ry&analysis.fieldtype=text_en
<br>>
<br>> Questions:
<br>>
<br>> 1. Is there a way to "load-balance" this? In the above url, I need to
<br>> specify a specific core. Is it possible to generalize it, so the core
<br>> that receives the request is not necessarily the one that processes
<br>> it? Or this already is distributed in a sense that receiving core and
<br>> processing cores are never the same?
<br>>
<br>> 2. The document was already analyze-chained. Is is possible to store
<br>> this information so one does not need to re-analyze-chain it once more?
<br>>
<br>> Cheers
<br>> Arturas
<br>>
<br>> On Fri, Mar 23, 2018 at 9:15 PM, Erick Erickson
<br>> <<a href="mailto:erickerickson@gmail.com">erickerickson@gmail.com</a>>
<br>> wrote:
<br>>
<br>>> Arturas:
<br>>>
<br>>> Try to field-qualify your hl.q parameter. That looks like:
<br>>>
<br>>> hl.q=trans:Kundigung
<br>>> or
<br>>> hl.q=trans:Kündigung
<br>>>
<br>>> I saw the exact behavior you describe when I did _not_ specify the
<br>>> field in the hl.q parameter, i.e.
<br>>>
<br>>> hl.q=Kundigung
<br>>> or
<br>>> hl.q=Kündigung
<br>>>
<br>>> didn't show all highlights.
<br>>>
<br>>> But when I did specify the field, it worked.
<br>>>
<br>>> Here's what I think is happening: Solr uses the default search field
<br>>> when parsing an un-field-qualified query. I.e.
<br>>>
<br>>> q=something
<br>>>
<br>>> is parsed as
<br>>>
<br>>> q=default_search_field:something.
<br>>>
<br>>> The default field is controlled in solrconfig.xml with the "df"
<br>>> parameter, you'll see entries like:
<br>>> <str name="df">my_field</str>
<br>>>
<br>>> Also when I changed the "df" parameter to the field I was
<br>>> highlighting on, I didn't need to specify the field on the hl.q
<br>parameter.
<br>>>
<br>>> hl.q=Kundigung
<br>>> or
<br>>> hl.q=Kündigung
<br>>>
<br>>> The default field is usually "text", which knows nothing about the
<br>>> German-specific filters you've applied unless you changed it.
<br>>>
<br>>> So in the absence of a field-qualification for the hl.q parameter
<br>>> Solr was parsing the query according to the analysis chain specifed
<br>>> in your default field, and probably passed ü through without
<br>>> transforming it. Since your indexing analysis chain for that field
<br>>> folded ü to just plain u, it wasn't found or highlighted.
<br>>>
<br>>> On the surface, this does seem like something that should be changed,
<br>>> I'll go ahead and ping the dev list.
<br>>>
<br>>> NOTE: I was trying this on Solr 7.1
<br>>>
<br>>> Best,
<br>>> Erick
<br>>>
<br>>> On Fri, Mar 23, 2018 at 12:03 PM, Arturas Mazeika <<a href="mailto:mazeika@gmail.com">mazeika@gmail.com</a>>
<br>>> wrote:
<br>>> > Hi Erick,
<br>>> >
<br>>> > Thanks for the update and the infos. Your post brought quite a bit
<br>>> > of
<br>>> light
<br>>> > into the picture and now I understand quite a bit more about what
<br>>> > you are saying. Your explanation makes sense and can be quite
<br>>> > useful in certain scenarious.
<br>>> >
<br>>> > What stroke me from your description is that you are saying that
<br>>> > the analyzer-chain needs to be applied for the highlighting queries as
<br>well.
<br>>> > The tragedy is that I am not able to get this for a german
<br>>> > collection: if the query is set (no explicit highlighting query),
<br>>> > the highlighting is correct. It is also correct, if I replace the
<br>>> > umaults into the corresponding latin chars. Getting the analyzer
<br>>> > chain for the
<br>>> highlighting
<br>>> > terms remains the challenge.
<br>>> >
<br>>> > Do you think you have a look at the following stakoverflow link?
<br>>> > Maybe something comes to your mind...
<br>>> >
<br>>> > *<a href="https://stackoverflow.com/questions/49276093/solr-">https://stackoverflow.com/questions/49276093/solr-</a>
<br>>> highlighting-terms-with-umlaut-not-found-not-highlighted
<br>>> > <<a href="https://stackoverflow.com/questions/49276093/solr-">https://stackoverflow.com/questions/49276093/solr-</a>
<br>>> highlighting-terms-with-umlaut-not-found-not-highlighted>*
<br>>> >
<br>>> > *Cheers,*
<br>>> >
<br>>> > *Arturas*
<br>>> > On Fri, Mar 23, 2018, 17:43 Erick Erickson
<br>>> > <<a href="mailto:erickerickson@gmail.com">erickerickson@gmail.com</a>>
<br>>> wrote:
<br>>> >
<br>>> >> bq: this is not a typical case that one searches for a keyword but
<br>>> >> highlights something else
<br>>> >>
<br>>> >> This isn't really an unusual case, apparently I mislead you.
<br>>> >>
<br>>> >> What I was trying to convey is that the analysis chain used is
<br>>> >> firmly attached to a particular _field_. There's no way to say
<br>>> >> "use one analysis chain for the query and another for highlighting
<br>>> >> on the _same_ field".
<br>>> >>
<br>>> >> You can use two different fields with different analysis chains,
<br>>> >> one for each purpose. So something like
<br>>> >>
<br>>> >> q=f1:something&hl.fl=f2,f3&hl.q=other
<br>>> >>
<br>>> >> is certainly reasonable. It'll search for "something" in f1, and
<br>>> >> highlight "other" in f2 and f3
<br>>> >>
<br>>> >> Each fields processes its input with the analysis chain defined in
<br>>> >> the schema.
<br>>> >>
<br>>> >> The rest about stored="true" can be ignored, it's just me
<br>>> >> wandering off into the weeds about an optimization that only
<br>>> >> stores the data once rather than redundantly in multiple fields.
<br>>> >>
<br>>> >> Best,
<br>>> >> Erick
<br>>> >>
<br>>> >> On Fri, Mar 23, 2018 at 4:37 AM, Arturas Mazeika
<br>>> >> <<a href="mailto:mazeika@gmail.com">mazeika@gmail.com</a>>
<br>>> >> wrote:
<br>>> >> > Hi Mathesis (Stefan),
<br>>> >> >
<br>>> >> > Thanks for the questions. This made me look at the problem from
<br>>> >> > a
<br>>> >> distance
<br>>> >> > and re-frame the situation. Good questions indeed.
<br>>> >> >
<br>>> >> > Trying to go around: consider a user who describes herself as
<br>>> >> > being a
<br>>> BMW
<br>>> >> > fan, being convinced that all BMW need to be the blackest color
<br>>> possible
<br>>> >> > (for a sake of argument) who would like to search and later
<br>>> >> > browse the entries in the discussion forum (of course not
<br>>> >> > everything but BMW of
<br>>> the
<br>>> >> > blackest color), and what interest her are the snippets that
<br>>> >> > have understood, craziest as keywords or the like (because she
<br>>> >> > is looking
<br>>> for
<br>>> >> a
<br>>> >> > dozen of discussions that she saw before).
<br>>> >> >
<br>>> >> > What I was not able to achieve so far is: (i) combine query term
<br>>> >> > for filtering and highlighting, (ii) using the analyzer-chain
<br>>> >> > from the attribute to rewrite the highlight query (or define one
<br>>> >> > in the search)
<br>>> >> >
<br>>> >> > CTR+F technique is a very powerful one, indeed. Works most of
<br>>> >> > CTR+the
<br>>> time.
<br>>> >> The
<br>>> >> > difficulties with it are query rewriting, enriching, etc.
<br>>> >> >
<br>>> >> > Cheers,
<br>>> >> > Arturas
<br>>> >> >
<br>>> >> > On Fri, Mar 23, 2018 at 11:29 AM, Stefan Matheis <
<br>>> >> <a href="mailto:matheis.stefan@gmail.com">matheis.stefan@gmail.com</a>>
<br>>> >> > wrote:
<br>>> >> >
<br>>> >> >> Perhaps we try it the other way round .. what's your use case
<br>>> >> >> for
<br>>> this?
<br>>> >> I'm
<br>>> >> >> trying to think of a situation where I'd need this a as user?
<br>>> >> >>
<br>>> >> >> The only reason I see myself doing this is CTRL+F in a page
<br>>> >> >> when the
<br>>> >> search
<br>>> >> >> result is not immediately visible for me ;)
<br>>> >> >>
<br>>> >> >> On Mar 23, 2018 9:41 AM, "Arturas Mazeika" <<a href="mailto:mazeika@gmail.com">mazeika@gmail.com</a>>
<br>>> wrote:
<br>>> >> >>
<br>>> >> >> > Hi Erick et al,
<br>>> >> >> >
<br>>> >> >> > From your answer I understand that this is not a typical case
<br>>> >> >> > that
<br>>> one
<br>>> >> >> > searches for a keyword but highlights something else. Since
<br>>> >> >> > we have
<br>>> >> two
<br>>> >> >> > parameters (q vs hl.q) I thought they are freely combinable.
<br>>> >> >> > From
<br>>> your
<br>>> >> >> > answer I understand that this is not really the case. My
<br>>> >> >> > current understanding came from [1] that says:
<br>>> >> >> >
<br>>> >> >> > hl.q
<br>>> >> >> >
<br>>> >> >> > A query to use for highlighting. This parameter allows you to
<br>>> >> highlight
<br>>> >> >> > different terms than those being used to retrieve documents.
<br>>> >> >> > what I hear from you is something different: i.e., that this
<br>>> >> >> > is not
<br>>> >> >> enough
<br>>> >> >> > just to combine the q with hl.q, that there are caveats to
<br>>> >> >> > achieve
<br>>> the
<br>>> >> >> task
<br>>> >> >> > (multiple fields, FastVectorHighlighter).
<br>>> >> >> >
<br>>> >> >> > Your infos are very helpful.
<br>>> >> >> >
<br>>> >> >> > Cheers,
<br>>> >> >> > Arturas
<br>>> >> >> >
<br>>> >> >> > [1]
<br>>> >> >> > <a href="https://lucene.apache.org/solr/guide/7_2/highlighting.html">https://lucene.apache.org/solr/guide/7_2/highlighting.html</a>
<br>>> >> >> >
<br>>> >> >> > On Thu, Mar 22, 2018 at 4:07 PM, Erick Erickson <
<br>>> >> <a href="mailto:erickerickson@gmail.com">erickerickson@gmail.com</a>
<br>>> >> >> >
<br>>> >> >> > wrote:
<br>>> >> >> >
<br>>> >> >> > > Basically you need to use a copyField, but in several variants:
<br>>> >> >> > >
<br>>> >> >> > > If you use the field _exclusively_ for highlighting then
<br>>> >> >> > > store
<br>>> the
<br>>> >> raw
<br>>> >> >> > > content there and have the field use whatever analyzer you
<br>want.
<br>>> You
<br>>> >> >> > > do _not_ need to have indexed="true" set for the field if
<br>>> >> >> > > you're highlighting on the fly. So you're searching against
<br>>> >> >> > > field1
<br>>> (which
<br>>> >> has
<br>>> >> >> > > indexed="true" stored="false" set) but highlighting against
<br>>> field2
<br>>> >> >> > > (which has indexed="false" stored="true" set). Of course
<br>>> >> >> > > any time
<br>>> >> you
<br>>> >> >> > > want to return the contents in a doc your fl needs to
<br>>> >> >> > > specify field2...
<br>>> >> >> > >
<br>>> >> >> > > The above does not bloat your index at all since the cost
<br>>> >> >> > > of stored="true" indexed="true" is the same as if you use
<br>>> >> >> > > two
<br>>> fields,
<br>>> >> >> > > each with only one option turned on.
<br>>> >> >> > >
<br>>> >> >> > > The second approach if you want to use
<br>>> >> >> > > FastVectorHighlighter or
<br>>> the
<br>>> >> >> > > like is simply to index both fields.
<br>>> >> >> > >
<br>>> >> >> > > Best,
<br>>> >> >> > > Erick
<br>>> >> >> > >
<br>>> >> >> > > On Thu, Mar 22, 2018 at 2:18 AM, Arturas Mazeika <
<br>>> <a href="mailto:mazeika@gmail.com">mazeika@gmail.com</a>
<br>>> >> >
<br>>> >> >> > > wrote:
<br>>> >> >> > > > Hi Solr-Users,
<br>>> >> >> > > >
<br>>> >> >> > > > I've been playing with a german collection of documents,
<br>>> >> >> > > > where
<br>>> I
<br>>> >> >> tried
<br>>> >> >> > to
<br>>> >> >> > > > search for one word (q=Tag) and highlighted another:
<br>>> >> >> (hl.q=Kundigung).
<br>>> >> >> > Is
<br>>> >> >> > > > this a "legal" use case? My key question is how can I
<br>>> >> >> > > > tell solr
<br>>> >> which
<br>>> >> >> > > query
<br>>> >> >> > > > analyzer to use for highlighting? Strictly speaking, I
<br>>> >> >> > > > should
<br>>> use
<br>>> >> >> > > > hl.q=Kündigung to conceptually look for relevant
<br>>> >> >> > > > information,
<br>>> but
<br>>> >> in
<br>>> >> >> > this
<br>>> >> >> > > > case, no highlighting is returned (as all umlauts are
<br>>> >> >> > > > left out
<br>>> in
<br>>> >> the
<br>>> >> >> > > > index) .
<br>>> >> >> > > >
<br>>> >> >> > > > Additional infos:
<br>>> >> >> > > >
<br>>> >> >> > > > solr version: 7.2
<br>>> >> >> > > > urls to query:
<br>>> >> >> > > >
<br>>> >> >> > > > <a href="http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=">http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=</a>
<br>>> >> >> > > true&hl.fl=trans&hl.q=Kundigung&hl.snippets=3&wt=xml&rows=1
<br>>> >> >> > > >
<br>>> >> >> > > > <a href="http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=">http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=</a>
<br>>> >> >> > > true&hl.fl=trans&hl.q=K%C3%BCndigung&hl.snippets=3&wt=xml&r
<br>>> >> >> > > ows=1
<br>>> >> >> > > > <<a href="http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=">http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=</a>
<br>>> >> >> > > true&hl.fl=trans&hl.q=Kundigung&hl.snippets=3&wt=xml&rows=1
<br>>> >> >> > > >
<br>>> >> >> > > >
<br>>> >> >> > > > Managed-schema:
<br>>> >> >> > > >
<br>>> >> >> > > > <fieldType name="text_de" class="solr.TextField"
<br>>> >> >> > > positionIncrementGap="100">
<br>>> >> >> > > > <analyzer>
<br>>> >> >> > > > <tokenizer class="solr.StandardTokenizerFactory"/>
<br>>> >> >> > > > <filter class="solr.LowerCaseFilterFactory"/>
<br>>> >> >> > > > <filter class="solr.StopFilterFactory"
<br>format="snowball"
<br>>> >> >> > > > words="lang/stopwords_de.txt" ignoreCase="true"/>
<br>>> >> >> > > > <filter class="solr.GermanNormalizationFilterFactory"/>
<br>>> >> >> > > > <filter class="solr.GermanLightStemFilterFactory"/>
<br>>> >> >> > > > </analyzer>
<br>>> >> >> > > > </fieldType>
<br>>> >> >> > > >
<br>>> >> >> > > >
<br>>> >> >> > > > Other additional infos:
<br>>> >> >> > > > <a href="https://stackoverflow.com/questions/49276093/solr-">https://stackoverflow.com/questions/49276093/solr-</a>
<br>>> >> >> > > highlighting-terms-with-umlaut-not-found-not-highlighted
<br>>> >> >> > > >
<br>>> >> >> > > > Cheers,
<br>>> >> >> > > > Arturas
<br>>> >> >> > >
<br>>> >> >> >
<br>>> >> >>
<br>>> >>
<br>>>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-86953943561390622752018-04-01T22:50:00.015-07:002018-04-01T22:51:32.107-07:00FW: Boosting Fields Based On The Query Provided-----Original Message-----
<br>From: Mukhopadhyay, Aratrika [mailto:<a href="mailto:Aratrika.Mukhopadhyay@mail.house.gov">Aratrika.Mukhopadhyay@mail.house.gov</a>]
<br>Sent: 22 March 2018 18:48
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: RE: Boosting Fields Based On The Query Provided
<br>
<br>Thanks for your reply Shawn. The query elevation worked for us. I have
<br>another question though. Right now I have ways to handle specific queries in
<br>the elevate.xml. The concern I am having is that I may have hundreds of
<br>queries that need to return different pages first. Is the only way to do
<br>this via the elevate.xml or is there a better approach for instance boosting
<br>fields ? When I am boosting fields in this fashion it is not working for me
<br>:
<br>
<br><requestHandler name="/select" class="solr.SearchHandler">
<br> <lst name="defaults">
<br> <str name="defType">edismax</str>
<br> <str name="qf"> url^50 host^30 content^20 title^10</str>
<br> </lst>
<br> <arr name="last-components">
<br> <str>elevator</str>
<br> </arr>
<br> </requestHandler>
<br>
<br>
<br>Thanks for your help .
<br>
<br>Aratrika Mukhopadhyay
<br>-----Original Message-----
<br>From: Shawn Heisey [mailto:<a href="mailto:apache@elyograg.org">apache@elyograg.org</a>]
<br>Sent: Tuesday, March 20, 2018 6:03 PM
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Boosting Fields Based On The Query Provided
<br>
<br>On 3/20/2018 2:25 PM, Mukhopadhyay, Aratrika wrote:
<br>> I have a solr query which I am having a hard time configuring as I
<br>would want it configured. Suppose I have a situation where I have two fields
<br>field1(host field) and field2 (url field). I want a specific host to be
<br>bubbled to the top for all terms except for when I am searching for specific
<br>people in which case I want the URL to their landing page returned first. I
<br>have configured the dismax query parser in my solrconfig but it seems that
<br>the boost being applied is arbitrary .
<br>
<br><snip>
<br>
<br>> <requestHandler name="/select" class="solr.SearchHandler">
<br>> <lst name="defaults">
<br>> <str name="defType">edismax</str>
<br>> <str name="q">*:*</str>
<br>> <str
<br>name="bq">host:(<a href="http://www.starwars.com">www.starwars.com</a>)^10</str<<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.starwars.com-29-255e10-253c_str&d=DwID-g&c=L93KkjKsAC98uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=QkEnIzj19X_nqC298QkAUDbjv_zmP1Xr9Vn_z6BQXoM&e=">https://urldefense.proofpoint.com/
<br>v2/url?u=http-3A__www.starwars.com-29-255e10-253c_str&d=DwID-g&c=L93KkjKsAC9
<br>8uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237
<br>NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=QkEn
<br>Izj19X_nqC298QkAUDbjv_zmP1Xr9Vn_z6BQXoM&e=</a> >>
<br>> <str name="q">Carrie Fisher</str>
<br>> <str name="bq">url:(
<br>http\:\/\/<a href="http://www.imdb.com">www.imdb.com</a>\/name\/nm0000402/<<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.imdb.com_name_nm0000402_&d=DwID-g&c=L93KkjKsAC98uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=ka0--rJJLml1zFZu_P1xPisIiLpXR5LwsIMm82TuoUk&e=">https://urldefense.proofpoint.com/v
<br>2/url?u=http-3A__www.imdb.com_name_nm0000402_&d=DwID-g&c=L93KkjKsAC98uTvC4Kv
<br>QDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMy
<br>iD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=ka0--rJJLml1
<br>zFZu_P1xPisIiLpXR5LwsIMm82TuoUk&e=</a> >)^8</str>
<br>> <str name="q">Mark Hamill</str>
<br>> <str name="bq">url:(
<br>http\:\/\/<a href="http://www.imdb.com">www.imdb.com</a>\/name\/nm0000434/<<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.imdb.com_name_nm0000434_&d=DwID-g&c=L93KkjKsAC98uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=sVRAvHN3kkJVjN8XTAWjZS85tUmOXp9W4exWvMPpGUk&e=">https://urldefense.proofpoint.com/v
<br>2/url?u=http-3A__www.imdb.com_name_nm0000434_&d=DwID-g&c=L93KkjKsAC98uTvC4Kv
<br>QDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMy
<br>iD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=sVRAvHN3kkJV
<br>jN8XTAWjZS85tUmOXp9W4exWvMPpGUk&e=</a> >)^8</str>
<br>> </lst>
<br>> </requestHandler>
<br>
<br>I think there's a fundamental misunderstanding of how "defaults" works.
<br>
<br>I have no idea what happens with multiple "q" parameters, which you have
<br>configured in defaults.  I do know that if your request includes a "q"
<br>parameter, then what you've put in defaults for "q" is going to be
<br>overridden and ignored.
<br>
<br>This section of the documentation covers defaults, appends, and invariants:
<br>
<br><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_solr_guide_6-5F6_requesthandlers-2Dand-2Dsearchcomponents-2Din-2Dsolrconfig.html-23RequestHandlersandSearchComponentsinSolrConfig-2DSearchHandlers&d=DwID-g&c=L93KkjKsAC98uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=LcNEhj3Y-S5KMW2HP0CG9t9UpRgEVsTcP7u8QgqW3tk&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_solr_
<br>guide_6-5F6_requesthandlers-2Dand-2Dsearchcomponents-2Din-2Dsolrconfig.html-
<br>23RequestHandlersandSearchComponentsinSolrConfig-2DSearchHandlers&d=DwID-g&c
<br>=L93KkjKsAC98uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWE
<br>y5WPCDMJD237NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegn
<br>w_nb0&s=LcNEhj3Y-S5KMW2HP0CG9t9UpRgEVsTcP7u8QgqW3tk&e=</a>
<br>
<br>I think the Query Elevation Component might be the kind of functionality
<br>you're after.  What you're trying to do with defaults is NOT going to work.
<br>
<br><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_solr_guide_6-5F6_the-2Dquery-2Delevation-2Dcomponent.html&d=DwID-g&c=L93KkjKsAC98uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237NoEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=I6TENNcAZab0ZE_j0tZ8hm8_7nuNFqhBwoey4Mm1T0E&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_solr_
<br>guide_6-5F6_the-2Dquery-2Delevation-2Dcomponent.html&d=DwID-g&c=L93KkjKsAC98
<br>uTvC4KvQDTmmq1mJ2vMPtzuTpFgX8gY&r=fbfOUDlf9NEzjz9RxL3c7eXnjEvWEy5WPCDMJD237N
<br>oEoCTMyiD1VH-RfTq9OP14&m=1RjiyUG9se2vpXYg-oLAiacdECUE6khXtuvegnw_nb0&s=I6TEN
<br>NcAZab0ZE_j0tZ8hm8_7nuNFqhBwoey4Mm1T0E&e=</a>
<br>
<br>Thanks,
<br>ShawnAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-81532645104538584392018-04-01T22:50:00.014-07:002018-04-01T22:51:30.188-07:00FW: Solr or Elasticsearch-----Original Message-----
<br>From: Steven White [mailto:<a href="mailto:swhite4141@gmail.com">swhite4141@gmail.com</a>]
<br>Sent: 22 March 2018 18:44
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Solr or Elasticsearch
<br>
<br>Hi everyone,
<br>
<br>There are some good write ups on the internet comparing the two and the one
<br>thing that keeps coming up about Elasticsearch being superior to Solr is
<br>it's analytic capability. However, I cannot find what those analytic
<br>capabilities are and why they cannot be done using Solr. Can someone help
<br>me with this question?
<br>
<br>Personally, I'm a Solr user and the thing that concerns me about
<br>Elasticsearch is the fact that it is owned by a company that can any day
<br>decide to stop making Elasticsearch avaialble under Apache license and even
<br>completely close free access to it.
<br>
<br>So, this is a 2 part question:
<br>
<br>1) What are the analytic capability of Elasticsearch that cannot be done
<br>using Solr? I want to see a complete list if possible.
<br>2) Should an Elasticsearch user be worried that Elasticsearch may close it's
<br>open-source policy at anytime or that outsiders have no say about it's road
<br>map?
<br>
<br>Thanks,
<br>
<br>SteveAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-44243355746516110102018-04-01T22:50:00.013-07:002018-04-01T22:51:28.535-07:00FW: querying vs. highlighting: complete freedom?-----Original Message-----
<br>From: Arturas Mazeika [mailto:<a href="mailto:mazeika@gmail.com">mazeika@gmail.com</a>]
<br>Sent: 22 March 2018 14:48
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: querying vs. highlighting: complete freedom?
<br>
<br>Hi Solr-Users,
<br>
<br>I've been playing with a german collection of documents, where I tried to
<br>search for one word (q=Tag) and highlighted another: (hl.q=Kundigung). Is
<br>this a "legal" use case? My key question is how can I tell solr which query
<br>analyzer to use for highlighting? Strictly speaking, I should use
<br>hl.q=Kündigung to conceptually look for relevant information, but in this
<br>case, no highlighting is returned (as all umlauts are left out in the
<br>index) .
<br>
<br>Additional infos:
<br>
<br>solr version: 7.2
<br>urls to query:
<br>
<br><a href="http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=true&hl.fl=trans&hl.q=Kundigung&hl.snippets=3&wt=xml&rows=1">http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=true&hl.fl=trans&hl.
<br>q=Kundigung&hl.snippets=3&wt=xml&rows=1</a>
<br>
<br><a href="http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=true&hl.fl=trans&hl.q=K%C3%BCndigung&hl.snippets=3&wt=xml&rows=1">http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=true&hl.fl=trans&hl.
<br>q=K%C3%BCndigung&hl.snippets=3&wt=xml&rows=1</a>
<br><<a href="http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=true&hl.fl=trans&hl.q=Kundigung&hl.snippets=3&wt=xml&rows=1">http://localhost:8983/solr/trans/select?q=trans:Zeit&hl=true&hl.fl=trans&hl
<br>.q=Kundigung&hl.snippets=3&wt=xml&rows=1</a>>
<br>
<br>Managed-schema:
<br>
<br> <fieldType name="text_de" class="solr.TextField"
<br>positionIncrementGap="100">
<br> <analyzer>
<br> <tokenizer class="solr.StandardTokenizerFactory"/>
<br> <filter class="solr.LowerCaseFilterFactory"/>
<br> <filter class="solr.StopFilterFactory" format="snowball"
<br>words="lang/stopwords_de.txt" ignoreCase="true"/>
<br> <filter class="solr.GermanNormalizationFilterFactory"/>
<br> <filter class="solr.GermanLightStemFilterFactory"/>
<br> </analyzer>
<br> </fieldType>
<br>
<br>
<br>Other additional infos:
<br><a href="https://stackoverflow.com/questions/49276093/solr-highlighting-terms-with-umlaut-not-found-not-highlighted">https://stackoverflow.com/questions/49276093/solr-highlighting-terms-with-um
<br>laut-not-found-not-highlighted</a>
<br>
<br>Cheers,
<br>ArturasAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-47790690208684809662018-04-01T22:50:00.012-07:002018-04-01T22:51:27.327-07:00FW: Get terms in solr not working-----Original Message-----
<br>From: Joel Bernstein [mailto:<a href="mailto:joelsolr@gmail.com">joelsolr@gmail.com</a>]
<br>Sent: 21 March 2018 20:51
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Get terms in solr not working
<br>
<br>Also what is the use case? What do you plan to do with terms? There may be
<br>other approaches that will work better then the terms query.
<br>
<br>Joel Bernstein
<br><a href="http://joelsolr.blogspot.com/">http://joelsolr.blogspot.com/</a>
<br>
<br>On Wed, Mar 21, 2018 at 9:28 AM, Erick Erickson <<a href="mailto:erickerickson@gmail.com">erickerickson@gmail.com</a>>
<br>wrote:
<br>
<br>> We need a lot more information. What is the exact query you're using?
<br>> Is 100M the number of docs? How many terms are in the field?
<br>>
<br>> On Tue, Mar 20, 2018 at 10:39 PM, adam rag <<a href="mailto:adamrag16@gmail.com">adamrag16@gmail.com</a>> wrote:
<br>> > To get top words in my Apache Solr instance, I am using "terms" query.
<br>> When
<br>> > I try it to get 10 terms in 100 million of data, the data are
<br>> > fetching after a few minutes, But if the data is 300 million the
<br>> > Solr is not responding. My server memory is 100 GB.
<br>>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-28952356959785127312018-04-01T22:50:00.011-07:002018-04-01T22:51:25.106-07:00FW: Upgrading a Plugin from 6.6 to 7.x-----Original Message-----
<br>From: Atita Arora [mailto:<a href="mailto:atitaarora@gmail.com">atitaarora@gmail.com</a>]
<br>Sent: 21 March 2018 19:01
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Upgrading a Plugin from 6.6 to 7.x
<br>
<br>Hi Peter,
<br>
<br>
<br>*(Sorry for the earlier incomplete email - I hit send by mistake)*
<br>
<br>I haven't really been able to look into it completely , but my first glance
<br>says , it should be because the method signature has changed.
<br>
<br>Iam looking here : <a href="https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/Query.html">https://lucene.apache.org/core/7_0_0/core/org/apache/
<br>lucene/search/Query.html</a>
<br>
<br>createWeight
<br><<a href="https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/Query.html#createWeight-org.apache.lucene.search.IndexSearcher-boolean-float-">https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/Query.ht
<br>ml#createWeight-org.apache.lucene.search.IndexSearcher-boolean-float-</a>>
<br>(IndexSearcher
<br><<a href="https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/IndexSearcher.html">https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/IndexSea
<br>rcher.html</a>>
<br> searcher, boolean needsScores, float boost)
<br>Expert: Constructs an appropriate Weight implementation for this query.
<br>
<br>While at :
<br>
<br><a href="https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/search/Query.htm">https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/search/Query.htm</a>
<br>l
<br>
<br>
<br>createWeight
<br><<a href="https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/search/Query.html#createWeight-org.apache.lucene.search.IndexSearcher-boolean-">https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/search/Query.ht
<br>ml#createWeight-org.apache.lucene.search.IndexSearcher-boolean-</a>>
<br>(IndexSearcher
<br><<a href="https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/search/IndexSearcher.html">https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/search/IndexSea
<br>rcher.html</a>>
<br>searcher,
<br>boolean needsScores)
<br>Expert: Constructs an appropriate Weight implementation for this query.
<br>
<br>You would need a code change for this to make it work in Version 7.
<br>
<br>Thanks,
<br>Atita
<br>
<br>
<br>On Wed, Mar 21, 2018 at 6:59 PM, Atita Arora <<a href="mailto:atitaarora@gmail.com">atitaarora@gmail.com</a>> wrote:
<br>
<br>> Hi Peter,
<br>>
<br>> I haven't really been able to look into it completely , but my first
<br>> glance says , it should be because the method signature has changed.
<br>>
<br>> Iam looking here :
<br>> <a href="https://lucene.apache.org/core/7_0_0/core/org/apache/">https://lucene.apache.org/core/7_0_0/core/org/apache/</a>
<br>> lucene/search/Query.html
<br>>
<br>> createWeight
<br>> <<a href="https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/Qu">https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/Qu</a>
<br>> ery.html#createWeight-org.apache.lucene.search.IndexSearcher-boolean-f
<br>> loat->
<br>> (IndexSearcher
<br>> <<a href="https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/In">https://lucene.apache.org/core/7_0_0/core/org/apache/lucene/search/In</a>
<br>> dexSearcher.html> searcher, boolean needsScores, float boost)
<br>> Expert: Constructs an appropriate Weight implementation for this query.
<br>>
<br>> While at :
<br>>
<br>>
<br>> On Wed, Mar 21, 2018 at 4:16 PM, Peter Alexander Kopciak
<br>> <<a href="mailto:peter@kopciak.at">peter@kopciak.at</a>
<br>> > wrote:
<br>>
<br>>> Hi!
<br>>>
<br>>> I'm still pretty new to Solr and I want to use the vector Scoring
<br>>> plugin (
<br>>> <a href="https://github.com/saaay71/solr-vector-scoring/network">https://github.com/saaay71/solr-vector-scoring/network</a>) but
<br>>> unfortunately, it does not seem to work for newer Solr versions.
<br>>>
<br>>> I tested it with 6.6 to verify its functionality, so it seems to be
<br>>> broken because of the upgrade to 7.x.
<br>>>
<br>>> When following the installation procedure and executing the examples,
<br>>> I ran into the following error with Query 1:
<br>>>
<br>>> java.lang.UnsupportedOperationException: Query {! type=vp f=vector
<br>>> vector=0.1,4.75,0.3,1.2,0.7,4.0 v=} does not implement createWeight
<br>>>
<br>>> Does anyone has a lead for me how to fix/upgrade the plugin? The
<br>>> createWeight method seems to exist, so I'm not sure where to start
<br>>> and waht the problem seems to be.
<br>>>
<br>>
<br>>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-12800440212837094002018-04-01T22:50:00.010-07:002018-04-01T22:51:23.302-07:00FW: Solr main replica down, another replica taking over-----Original Message-----
<br>From: Shawn Heisey [mailto:<a href="mailto:apache@elyograg.org">apache@elyograg.org</a>]
<br>Sent: 21 March 2018 18:37
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Solr main replica down, another replica taking over
<br>
<br>On 3/21/2018 12:04 AM, Midas A wrote:
<br>> We want to send less traffic over virtual machines and more on
<br>> physical servers . How can we achieve this
<br>
<br>At the moment, I do not know of any functionality in SolrCloud to accomplish
<br>this goal.  As I mentioned before, there is work underway to make it
<br>possible, but it's not available yet.
<br>
<br>One thing you could do is include preferLocalShards=true as a URL parameter
<br>and only send requests to the physical servers (unless they are down), but
<br>to do that, you'll have to handle load balancing yourself.
<br>
<br>Thanks,
<br>ShawnAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-16978767425414423622018-04-01T22:50:00.009-07:002018-04-01T22:51:18.966-07:00FW: [PHP Classes] Notable PHP package: PHP DNS Check Tool<div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ascii-theme-font:minor-latin;mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Mangal;mso-bidi-theme-font:minor-bidi;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ascii-theme-font:minor-latin;mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Mangal;mso-bidi-theme-font:minor-bidi;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><a name="_MailOriginal"><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US'>From:</span></b></a><span style='mso-bookmark:_MailOriginal'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US'> PHP Classes Notable [mailto:list-notable@phpclasses.org] <br><b>Sent:</b> 21 March 2018 12:22<br><b>To:</b> ROSHAN <roshan@siddhast.com><br><b>Subject:</b> [PHP Classes] Notable PHP package: PHP DNS Check Tool<o:p></o:p></span></span></p></div></div><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><o:p> </o:p></span></p><div><p class=MsoNormal style='mso-line-height-alt:.75pt'><span style='mso-bookmark:_MailOriginal'><span lang=EN style='font-size:1.0pt;mso-fareast-font-family:"Times New Roman";color:#333333;mso-ansi-language:EN'>A DNS is a server hosted in the Internet that can return IP addresses of other computers also on the Internet. Often computers need to query different DNS servers to obtain the IP addresses of same computers, but since the information may not be synchronized, there may be differences between the record values. This package can determine if there are differences between the values of given records stored in different DNS servers.<o:p></o:p></span></span></p></div><div><div id=MainContainer><div id=Container><div id=PageInfo><div id=Top><div style='mso-element:para-border-div;border:none;border-bottom:dotted #CCCCCC 2.25pt;padding:0cm 0cm 0cm 0cm;background:white;margin-left:22.5pt;margin-right:0cm'><p class=MsoNormal align=center style='text-align:center;line-height:15.0pt;mso-outline-level:2;background:white;border:none;mso-border-bottom-alt:dotted #CCCCCC 2.25pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 0cm'><span style='mso-bookmark:_MailOriginal'><b><span lang=EN style='font-size:15.0pt;mso-fareast-font-family:"Times New Roman";color:#666666;mso-font-kerning:18.0pt;mso-ansi-language:EN'>Notable PHP package: PHP DNS Check Tool<o:p></o:p></span></b></span></p></div></div><div id=ads><p class=MsoNormal style='background:white'><span style='mso-bookmark:_MailOriginal'><span lang=EN style='mso-fareast-font-family:"Times New Roman";color:black;border:solid windowtext 1.0pt;padding:0cm;mso-ansi-language:EN'><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIS3aAU8hK0UViF0Y2e1n8E1Ij1vEs8kAaP6cXSr5xGQ_YbNUSgh5OHE1KrV1MvgvXAjyqdmDs-PQ8l6nH7Ka1PgIafN1HX7UMcBV9318yDt5kf4b305dnYewLSLxEw0BcANWBh3PI3Cie/s1600/%257EWRD241-778972.jpg"><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIS3aAU8hK0UViF0Y2e1n8E1Ij1vEs8kAaP6cXSr5xGQ_YbNUSgh5OHE1KrV1MvgvXAjyqdmDs-PQ8l6nH7Ka1PgIafN1HX7UMcBV9318yDt5kf4b305dnYewLSLxEw0BcANWBh3PI3Cie/s320/%257EWRD241-778972.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_6539724563669562498" /></a></span></span><span style='mso-bookmark:_MailOriginal'><span lang=EN style='mso-fareast-font-family:"Times New Roman";color:black;mso-ansi-language:EN'><o:p></o:p></span></span></p><div align=center><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=0 style='width:351.0pt;mso-cellspacing:0cm;mso-yfti-tbllook:1184;mso-padding-alt:0cm 0cm 0cm 0cm'><tr style='mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes'><td style='padding:0cm 0cm 0cm 0cm'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'></span><a href="https://www.phpclasses.org/open/h/9b43c6/ub/cm9zaGFuQHNpZGRoYXN0LmNvbQ%3D%3D/urlb/aHR0cDovL3d3dy5sYXVuY2hiaXQuY29tL2FiLzEwOWZiNThkZmQv/id/50459/l/notable/c/c.html"><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";border:solid windowtext 1.0pt;padding:0cm;text-decoration:none;text-underline:none'><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter" /> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0" /> <v:f eqn="sum @0 1 0" /> <v:f eqn="sum 0 0 @1" /> <v:f eqn="prod @2 1 2" /> <v:f eqn="prod @3 21600 pixelWidth" /> <v:f eqn="prod @3 21600 pixelHeight" /> <v:f eqn="sum @0 0 1" /> <v:f eqn="prod @6 1 2" /> <v:f eqn="prod @7 21600 pixelWidth" /> <v:f eqn="sum @8 21600 0" /> <v:f eqn="prod @7 21600 pixelHeight" /> <v:f eqn="sum @10 21600 0" /> </v:formulas> <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" /> <o:lock v:ext="edit" aspectratio="t" /> </v:shapetype><v:shape id="_x0000_i1026" type="#_x0000_t75" alt="Image removed by sender." href="https://www.phpclasses.org/open/h/9b43c6/ub/cm9zaGFuQHNpZGRoYXN0LmNvbQ%3D%3D/urlb/aHR0cDovL3d3dy5sYXVuY2hiaXQuY29tL2FiLzEwOWZiNThkZmQv/id/50459/l/notable/c/c.html" style='width:93.75pt;height:93.75pt' o:button="t"> <v:imagedata src="cid:~WRD241.jpg" o:href="cid:~WRD241.jpg" /> </v:shape><![endif]--><![if !vml]><span style='mso-ignore:vglayout'><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg28pDL0ib9d2k2jFomj9-Vnk5LOqXOD3zE3NO6tcF-SIxJmYcTL1bzAeeUq7iho6PMaCUMIe7aCvByrVocA-YL07PS6Zx0fsEVKH7oJTsLzcXEo4N_3WlstN9EH6tbsM_lH3TUU4vLeJch/s1600/image001-780747.jpg"><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg28pDL0ib9d2k2jFomj9-Vnk5LOqXOD3zE3NO6tcF-SIxJmYcTL1bzAeeUq7iho6PMaCUMIe7aCvByrVocA-YL07PS6Zx0fsEVKH7oJTsLzcXEo4N_3WlstN9EH6tbsM_lH3TUU4vLeJch/s320/image001-780747.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_6539724569322117410" /></a></span><![endif]></span></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'><o:p></o:p></span></span></p></td><span style='mso-bookmark:_MailOriginal'></span><td style='padding:3.0pt 3.0pt 3.0pt 3.0pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'></span><a href="https://www.phpclasses.org/open/h/9b43c6/ub/cm9zaGFuQHNpZGRoYXN0LmNvbQ%3D%3D/urlb/aHR0cDovL3d3dy5sYXVuY2hiaXQuY29tL2FiLzEwOWZiNThkZmQv/id/50459/l/notable/c/c.html"><span style='mso-bookmark:_MailOriginal'><b><span style='font-size:10.5pt;font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>Replay Real User Sessions</span></b></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'><br><br>Monitor and Replay what Real Users do on your Website or Web app<o:p></o:p></span></span></p></td><span style='mso-bookmark:_MailOriginal'></span></tr></table></div></div><div align=center><table class=MsoNormalTable border=1 cellpadding=0 style='mso-cellspacing:1.5pt;border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;mso-yfti-tbllook:1184;mso-padding-alt:7.5pt 7.5pt 7.5pt 7.5pt'><tr style='mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes'><td style='border:none;padding:7.5pt 7.5pt 7.5pt 3.75pt'><h4><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>ROSHAN, a PHP package is considered Notable when it does something different that is worth noting.<o:p></o:p></span></span></h4><p><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black'>If you have also written Notable packages, </span></span><a href="https://www.phpclasses.org/contribute.html"><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif'>contribute</span></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black'> them to the PHP Classes site to get your work more exposure.<br><br>If your notable package is innovative, you may also earn prizes and recognition in the </span></span><a href="https://www.phpclasses.org/winners/"><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif'>PHP Innovation Award</span></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black'>.<o:p></o:p></span></span></p><div style='mso-element:para-border-div;border:solid yellow 3.0pt;padding:3.0pt 3.0pt 3.0pt 3.0pt;background:yellow'><p style='background:yellow;border:none;mso-border-alt:solid yellow 3.0pt;padding:0cm;mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt;border-radius: 8px'><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black'>Now you can also win a Big elePHPant as one of the possible prizes you can win every month. Check the complete list of prizes here: </span></span><a href="https://www.phpclasses.org/award/innovation/#sponsors-and-prizes"><span style='mso-bookmark:_MailOriginal'><b><span style='font-family:"Arial",sans-serif'>List of prizes</span></b></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black'><o:p></o:p></span></span></p></div><p><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black;border:solid windowtext 1.0pt;padding:0cm'><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIS3aAU8hK0UViF0Y2e1n8E1Ij1vEs8kAaP6cXSr5xGQ_YbNUSgh5OHE1KrV1MvgvXAjyqdmDs-PQ8l6nH7Ka1PgIafN1HX7UMcBV9318yDt5kf4b305dnYewLSLxEw0BcANWBh3PI3Cie/s1600/%257EWRD241-778972.jpg"><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIS3aAU8hK0UViF0Y2e1n8E1Ij1vEs8kAaP6cXSr5xGQ_YbNUSgh5OHE1KrV1MvgvXAjyqdmDs-PQ8l6nH7Ka1PgIafN1HX7UMcBV9318yDt5kf4b305dnYewLSLxEw0BcANWBh3PI3Cie/s320/%257EWRD241-778972.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_6539724563669562498" /></a></span></span><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;color:black'><o:p></o:p></span></span></p></td><span style='mso-bookmark:_MailOriginal'></span></tr></table></div><p class=MsoNormal align=center style='text-align:center;background:white'><span style='mso-bookmark:_MailOriginal'><span lang=EN style='mso-fareast-font-family:"Times New Roman";color:black;display:none;mso-hide:all;mso-ansi-language:EN'><o:p> </o:p></span></span></p><div align=center><table class=MsoNormalTable border=0 cellpadding=0 style='mso-cellspacing:1.5pt;mso-yfti-tbllook:1184;max-width: 40em'><tr style='mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes'><td style='padding:.75pt .75pt .75pt 3.75pt'><h2><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>Package<o:p></o:p></span></span></h2><div style='border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;padding:8.0pt 8.0pt 8.0pt 8.0pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'></span><a href="https://www.phpclasses.org/package/10676-PHP-Check-DNS-records-and-compare-record-sets.html"><span style='mso-bookmark:_MailOriginal'><b><span style='font-size:10.5pt;font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>PHP DNS Check Tool</span></b></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'><br><br>Check DNS records and compare record sets<o:p></o:p></span></span></p></div><h2><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>Moderator comment<o:p></o:p></span></span></h2><div style='border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;padding:8.0pt 8.0pt 8.0pt 8.0pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><b><span style='font-size:13.5pt;font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'>A DNS is a server hosted in the Internet that can return IP addresses of other computers also on the Internet.<br><br>Often computers need to query different DNS servers to obtain the IP addresses of same computers, but since the information may not be synchronized, there may be differences between the record values.<br><br>This package can determine if there are differences between the values of given records stored in different DNS servers.</span></b></span><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'><o:p></o:p></span></span></p></div><h2><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>Author<o:p></o:p></span></span></h2><div style='border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;padding:8.0pt 8.0pt 8.0pt 8.0pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'>Matous Nemec<o:p></o:p></span></span></p></div><h2><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>Groups<o:p></o:p></span></span></h2><div style='border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;padding:8.0pt 8.0pt 8.0pt 8.0pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'>Networking, PHP 7<o:p></o:p></span></span></p></div><h2><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>Description<o:p></o:p></span></span></h2><div style='border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;padding:8.0pt 8.0pt 8.0pt 8.0pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'>This class can check DNS records and compare record sets.<br><br>It can perform lookups to DNS servers to obtain the values of record for certain domains and of certain record types.<br><br>The class can also compare sets of records obtained from different providers like DNS servers or arrays to determine the differences and see what changed.<o:p></o:p></span></span></p></div></td><span style='mso-bookmark:_MailOriginal'></span></tr></table></div><p class=MsoNormal align=center style='text-align:center;background:white'><span style='mso-bookmark:_MailOriginal'><span lang=EN style='mso-fareast-font-family:"Times New Roman";color:black;display:none;mso-hide:all;mso-ansi-language:EN'><o:p> </o:p></span></span></p><div align=center><table class=MsoNormalTable border=1 cellpadding=0 style='mso-cellspacing:1.5pt;border-top:#E1E1E1;border-left:#E1E1E1;border-bottom:#999999;border-right:#999999;border-style:solid;border-width:1.0pt;mso-border-top-alt:#E1E1E1;mso-border-left-alt:#E1E1E1;mso-border-bottom-alt:#999999;mso-border-right-alt:#999999;mso-border-style-alt:solid;mso-border-width-alt:.75pt;mso-yfti-tbllook:1184;mso-padding-alt:7.5pt 7.5pt 7.5pt 7.5pt;max-width: 40em'><tr style='mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes'><td style='border:none;padding:7.5pt 7.5pt 7.5pt 3.75pt'><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'>ROSHAN you are getting this message as free service for being a user of the PHP Classes site to which you registered voluntarily using the email address roshan@siddhast.com. If you wish to unsubscribe go to the </span></span><a href="https://www.phpclasses.org/unsub/n/siddhast/u/notable/cc/ae5bc9/"><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman"'>unsubscribe page</span></span><span style='mso-bookmark:_MailOriginal'></span></a><span style='mso-bookmark:_MailOriginal'><span style='font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman";color:black'>.<o:p></o:p></span></span></p></td><span style='mso-bookmark:_MailOriginal'></span></tr></table></div></div></div></div></div><p class=MsoNormal><span style='mso-bookmark:_MailOriginal'><span lang=EN style='mso-fareast-font-family:"Times New Roman";border:solid windowtext 1.0pt;padding:0cm;mso-ansi-language:EN'><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIS3aAU8hK0UViF0Y2e1n8E1Ij1vEs8kAaP6cXSr5xGQ_YbNUSgh5OHE1KrV1MvgvXAjyqdmDs-PQ8l6nH7Ka1PgIafN1HX7UMcBV9318yDt5kf4b305dnYewLSLxEw0BcANWBh3PI3Cie/s1600/%257EWRD241-778972.jpg"><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIS3aAU8hK0UViF0Y2e1n8E1Ij1vEs8kAaP6cXSr5xGQ_YbNUSgh5OHE1KrV1MvgvXAjyqdmDs-PQ8l6nH7Ka1PgIafN1HX7UMcBV9318yDt5kf4b305dnYewLSLxEw0BcANWBh3PI3Cie/s320/%257EWRD241-778972.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_6539724563669562498" /></a></span></span><span style='mso-bookmark:_MailOriginal'></span><span lang=EN style='mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN'><o:p></o:p></span></p></div>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-16626828807839861782018-04-01T22:50:00.008-07:002018-04-01T22:51:16.412-07:00FW: Solrj Analytics component-----Original Message-----
<br>From: Jason Gerlowski [mailto:<a href="mailto:gerlowskija@gmail.com">gerlowskija@gmail.com</a>]
<br>Sent: 21 March 2018 04:07
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: Solrj Analytics component
<br>
<br>Hi Asmaa,
<br>
<br>As far as I know, there aren't any SolrJ classes built expressly for
<br>Analytics component requests like what exists for the Collection Admin APIs,
<br>etc.
<br>(<a href="https://lucene.apache.org/solr/7_2_0/solr-solrj/org/apache/solr/client/solrj/request/CollectionAdminRequest.html">https://lucene.apache.org/solr/7_2_0/solr-solrj/org/apache/solr/client/solr
<br>j/request/CollectionAdminRequest.html</a>).
<br>But it should still be possible to package your request into a SolrRequest
<br>via some of the setters on that object, and parse the response out of the
<br>returned NamedList<Object>.
<br>
<br>It isn't pretty, but it _should_ be possible. Was there a more specific
<br>aspect of building the request that you were getting hung up on?
<br>
<br>
<br>Best of luck,
<br>
<br>Jason
<br>
<br>On Fri, Mar 16, 2018 at 4:38 PM, Asmaa Shoala <<a href="mailto:asmaa.shoala@nm-eg.com">asmaa.shoala@nm-eg.com</a>>
<br>wrote:
<br>> Hello,
<br>>
<br>> I want to use analytics
<br>component(<a href="https://lucene.apache.org/solr/guide/7_2/analytics.html#analytic-pivot-facets">https://lucene.apache.org/solr/guide/7_2/analytics.html#analytic-p
<br>ivot-facets</a>) in java code but i didn't find any guide over the internet .
<br>>
<br>> Can you please help me?
<br>>
<br>> Thanks,
<br>>
<br>> Asmaa Ramzy Shoala
<br>>
<br>> novomind Egypt LLC
<br>> _____________________________
<br>>
<br>> 7 Abou Rafea Street, Moustafa Kamel, Alexandria, Egypt
<br>>
<br>> Mobile +20 1227281143
<br>> email <a href="mailto:asmaa.shoala@nm-eg.com">asmaa.shoala@nm-eg.com</a><mailto:<a href="mailto:asmaa.shoala@nm-eg.com">asmaa.shoala@nm-eg.com</a>> . Skype
<br>> asmaa.shoala_nmeg
<br>>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-49807681924088191972018-04-01T22:50:00.007-07:002018-04-01T22:51:14.835-07:00FW: Boosting Fields Based On The Query Provided -----Original Message-----
<br>From: Mukhopadhyay, Aratrika [mailto:<a href="mailto:Aratrika.Mukhopadhyay@mail.house.gov">Aratrika.Mukhopadhyay@mail.house.gov</a>]
<br>Sent: 21 March 2018 01:56
<br>To: '<a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>' <<a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>>
<br>Subject: Boosting Fields Based On The Query Provided
<br>
<br>All ,
<br> I have a solr query which I am having a hard time configuring as I
<br>would want it configured. Suppose I have a situation where I have two fields
<br>field1(host field) and field2 (url field). I want a specific host to be
<br>bubbled to the top for all terms except for when I am searching for specific
<br>people in which case I want the URL to their landing page returned first. I
<br>have configured the dismax query parser in my solrconfig but it seems that
<br>the boost being applied is arbitrary .
<br>
<br>To be more specific if I search for terms related to star wars I want to
<br>boost the <a href="http://starwars.com">starwars.com</a> domain but if I search for Carrie Fisher or Mark
<br>Hamill I want to boost the url <a href="http://www.imdb.com/name/nm0000402/">http://www.imdb.com/name/nm0000402/</a> (Carrie
<br>Fisher's imdb page) to the top for Carrie fisher and the url
<br><a href="http://www.imdb.com/name/nm0000434/">http://www.imdb.com/name/nm0000434/</a> (Mark Hamill's imdb page) to the top for
<br>Mark Hamill . Here would be my current configuration which is not working .
<br>
<br> <requestHandler name="/select" class="solr.SearchHandler">
<br> <lst name="defaults">
<br> <str name="defType">edismax</str>
<br> <str name="q">*:*</str>
<br> <str
<br>name="bq">host:(<a href="http://www.starwars.com">www.starwars.com</a>)^10</str<<a href="http://www.starwars.com">http://www.starwars.com</a>)%5e10%3c/s
<br>tr>>
<br> <str name="q">Carrie Fisher</str>
<br> <str name="bq">url:(
<br>http\:\/\/<a href="http://www.imdb.com">www.imdb.com</a>\/name\/nm0000402/<<a href="http://www.imdb.com/name/nm0000402/">http://www.imdb.com/name/nm0000402/</a>
<br>>)^8</str>
<br> <str name="q">Mark Hamill</str>
<br> <str name="bq">url:(
<br>http\:\/\/<a href="http://www.imdb.com">www.imdb.com</a>\/name\/nm0000434/<<a href="http://www.imdb.com/name/nm0000434/">http://www.imdb.com/name/nm0000434/</a>
<br>>)^8</str>
<br> </lst>
<br> </requestHandler>
<br>
<br>Do any of you know how to best handle a case like this ?
<br>
<br>Regards,
<br>Aratrika MukhopadhyayAnonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-4930975673032591892018-04-01T22:50:00.006-07:002018-04-01T22:51:13.216-07:00FW: CDCR Invalid Number on deletes-----Original Message-----
<br>From: Amrit Sarkar [mailto:<a href="mailto:sarkaramrit2@gmail.com">sarkaramrit2@gmail.com</a>]
<br>Sent: 21 March 2018 01:20
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: Re: CDCR Invalid Number on deletes
<br>
<br>Hi Chris,
<br>
<br>Sorry I was off work for few days and didn't follow the conversation. The
<br>link is directing me to
<br><a href="https://issues.apache.org/jira/projects/SOLR/issues/SOLR-12063">https://issues.apache.org/jira/projects/SOLR/issues/SOLR-12063</a>. I think we
<br>have fixed the issue stated by you in the jira, though the symptoms were
<br>different than yours.
<br>
<br>Amrit Sarkar
<br>Search Engineer
<br>Lucidworks, Inc.
<br>415-589-9269
<br><a href="http://www.lucidworks.com">www.lucidworks.com</a>
<br>Twitter <a href="http://twitter.com/lucidworks">http://twitter.com/lucidworks</a>
<br>LinkedIn: <a href="https://www.linkedin.com/in/sarkaramrit2">https://www.linkedin.com/in/sarkaramrit2</a>
<br>Medium: <a href="https://medium.com/@sarkaramrit2">https://medium.com/@sarkaramrit2</a>
<br>
<br>On Wed, Mar 21, 2018 at 1:17 AM, Chris Troullis <<a href="mailto:cptroullis@gmail.com">cptroullis@gmail.com</a>>
<br>wrote:
<br>
<br>> Nevermind I found it....the link you posted links me to SOLR-12036
<br>> instead of SOLR-12063 for some reason.
<br>>
<br>> On Tue, Mar 20, 2018 at 1:51 PM, Chris Troullis <<a href="mailto:cptroullis@gmail.com">cptroullis@gmail.com</a>>
<br>> wrote:
<br>>
<br>> > Hey Amrit,
<br>> >
<br>> > Did you happen to see my last reply? Is SOLR-12036 the correct JIRA?
<br>> >
<br>> > Thanks,
<br>> >
<br>> > Chris
<br>> >
<br>> > On Wed, Mar 7, 2018 at 1:52 PM, Chris Troullis
<br>> > <<a href="mailto:cptroullis@gmail.com">cptroullis@gmail.com</a>>
<br>> > wrote:
<br>> >
<br>> >> Hey Amrit, thanks for the reply!
<br>> >>
<br>> >> I checked out SOLR-12036, but it doesn't look like it has to do
<br>> >> with CDCR, and the patch that is attached doesn't look CDCR
<br>> >> related. Are you sure that's the correct JIRA number?
<br>> >>
<br>> >> Thanks,
<br>> >>
<br>> >> Chris
<br>> >>
<br>> >> On Wed, Mar 7, 2018 at 11:21 AM, Amrit Sarkar
<br>> >> <<a href="mailto:sarkaramrit2@gmail.com">sarkaramrit2@gmail.com</a>>
<br>> >> wrote:
<br>> >>
<br>> >>> Hey Chris,
<br>> >>>
<br>> >>> I figured a separate issue while working on CDCR which may relate
<br>> >>> to
<br>> your
<br>> >>> problem. Please see jira: *SOLR-12063*
<br>> >>> <<a href="https://issues.apache.org/jira/projects/SOLR/issues/SOLR-12063">https://issues.apache.org/jira/projects/SOLR/issues/SOLR-12063</a>>.
<br>> >>> This is a bug got introduced when we supported the bidirectional
<br>> >>> approach where
<br>> an
<br>> >>> extra flag in tlog entry for cdcr is added.
<br>> >>>
<br>> >>> This part of the code is messing up:
<br>> >>> *UpdateLog.java.RecentUpdates::update()::*
<br>> >>>
<br>> >>> switch (oper) {
<br>> >>> case UpdateLog.ADD:
<br>> >>> case UpdateLog.UPDATE_INPLACE:
<br>> >>> case UpdateLog.DELETE:
<br>> >>> case UpdateLog.DELETE_BY_QUERY:
<br>> >>> Update update = new Update();
<br>> >>> update.log = oldLog;
<br>> >>> update.pointer = reader.position();
<br>> >>> update.version = version;
<br>> >>>
<br>> >>> if (oper == UpdateLog.UPDATE_INPLACE && entry.size() == 5) {
<br>> >>> update.previousVersion = (Long)
<br>> >>> entry.get(UpdateLog.PREV_VERSI ON_IDX);
<br>> >>> }
<br>> >>> updatesForLog.add(update);
<br>> >>> updates.put(version, update);
<br>> >>>
<br>> >>> if (oper == UpdateLog.DELETE_BY_QUERY) {
<br>> >>> deleteByQueryList.add(update);
<br>> >>> } else if (oper == UpdateLog.DELETE) {
<br>> >>> deleteList.add(new DeleteUpdate(version,
<br>> >>> (byte[])entry.get(entry.size()-1)));
<br>> >>> }
<br>> >>>
<br>> >>> break;
<br>> >>>
<br>> >>> case UpdateLog.COMMIT:
<br>> >>> break;
<br>> >>> default:
<br>> >>> throw new SolrException(SolrException.ErrorCode.SERVER_ERROR,
<br>> >>> "Unknown Operation! " + oper);
<br>> >>> }
<br>> >>>
<br>> >>> deleteList.add(new DeleteUpdate(version,
<br>> >>> (byte[])entry.get(entry.size() -1)));
<br>> >>>
<br>> >>> is expecting the last entry to be the payload, but everywhere in
<br>> >>> the project, *pos:[2] *is the index for the payload, while the
<br>> >>> last entry
<br>> in
<br>> >>> source code is *boolean* in / after Solr 7.2, denoting update is
<br>> >>> cdcr forwarded or typical. UpdateLog.java.RecentUpdates is used to
<br>> >>> in cdcr sync, checkpoint operations and hence it is a legit bug,
<br>> >>> slipped the tests I wrote.
<br>> >>>
<br>> >>> The immediate fix patch is uploaded and I am awaiting feedback on
<br>that.
<br>> >>> Meanwhile if it is possible for you to apply the patch, build the
<br>> >>> jar
<br>> and
<br>> >>> try it out, please do and let us know.
<br>> >>>
<br>> >>> For, *SOLR-9394*
<br>> >>> <<a href="https://issues.apache.org/jira/browse/SOLR-9394">https://issues.apache.org/jira/browse/SOLR-9394</a>>, if you can
<br>> >>> comment on the JIRA and post the sample docs, solr logs, relevant
<br>> >>> information, I can give it a thorough look.
<br>> >>>
<br>> >>> Amrit Sarkar
<br>> >>> Search Engineer
<br>> >>> Lucidworks, Inc.
<br>> >>> 415-589-9269
<br>> >>> <a href="http://www.lucidworks.com">www.lucidworks.com</a>
<br>> >>> Twitter <a href="http://twitter.com/lucidworks">http://twitter.com/lucidworks</a>
<br>> >>> LinkedIn: <a href="https://www.linkedin.com/in/sarkaramrit2">https://www.linkedin.com/in/sarkaramrit2</a>
<br>> >>> Medium: <a href="https://medium.com/@sarkaramrit2">https://medium.com/@sarkaramrit2</a>
<br>> >>>
<br>> >>> On Wed, Mar 7, 2018 at 1:35 AM, Chris Troullis
<br>> >>> <<a href="mailto:cptroullis@gmail.com">cptroullis@gmail.com</a>>
<br>> >>> wrote:
<br>> >>>
<br>> >>> > Hi all,
<br>> >>> >
<br>> >>> > We recently upgraded to Solr 7.2.0 as we saw that there were
<br>> >>> > some
<br>> CDCR
<br>> >>> bug
<br>> >>> > fixes and features added that would finally let us be able to
<br>> >>> > make
<br>> use
<br>> >>> of
<br>> >>> > it (bi-directional syncing was the big one). The first time we
<br>> >>> > tried
<br>> to
<br>> >>> > implement we ran into all kinds of errors, but this time we were
<br>> >>> > able
<br>> >>> to
<br>> >>> > get it mostly working.
<br>> >>> >
<br>> >>> > The issue we seem to be having now is that any time a document
<br>> >>> > is
<br>> >>> deleted
<br>> >>> > via deleteById from a collection on the primary node, we are
<br>> >>> > flooded
<br>> >>> with
<br>> >>> > "Invalid Number" errors followed by a random sequence of
<br>> >>> > characters
<br>> >>> when
<br>> >>> > CDCR tries to sync the update to the backup site. This happens
<br>> >>> > on all
<br>> >>> of
<br>> >>> > our collections where our id fields are defined as longs (some
<br>> >>> > of
<br>> them
<br>> >>> the
<br>> >>> > ids are compound keys and are strings).
<br>> >>> >
<br>> >>> > Here's a sample exception:
<br>> >>> >
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
<br>> >>> Error
<br>> >>> > from server at <a href="http://ip/solr/collection_shard1_replica_n1">http://ip/solr/collection_shard1_replica_n1</a>:
<br>> >>> > Invalid
<br>> >>> > Number: ]
<br>> >>> > -s
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > directUpdate(CloudSolrClient.java:549)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > sendRequest(CloudSolrClient.java:1012)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > requestWithRetryOnStaleState(CloudSolrClient.java:883)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > requestWithRetryOnStaleState(CloudSolrClient.java:945)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > requestWithRetryOnStaleState(CloudSolrClient.java:945)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > requestWithRetryOnStaleState(CloudSolrClient.java:945)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > requestWithRetryOnStaleState(CloudSolrClient.java:945)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.
<br>> >>> > requestWithRetryOnStaleState(CloudSolrClient.java:945)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.impl.CloudSolrClient.request(
<br>> >>> > CloudSolrClient.java:816)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.SolrRequest.process(
<br>> SolrRequest.java:194)
<br>> >>> > at
<br>> >>> > org.apache.solr.client.solrj.SolrRequest.process(
<br>> SolrRequest.java:211)
<br>> >>> > at
<br>> >>> > org.apache.solr.handler.CdcrReplicator.sendRequest(
<br>> >>> > CdcrReplicator.java:140)
<br>> >>> > at
<br>> >>> > org.apache.solr.handler.CdcrReplicator.run(CdcrReplicator.java:104)
<br>> >>> > at
<br>> >>> > org.apache.solr.handler.CdcrReplicatorScheduler.lambda$null$0(
<br>> >>> > CdcrReplicatorScheduler.java:81)
<br>> >>> > at
<br>> >>> > org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.
<br>> >>> > lambda$execute$0(ExecutorUtil.java:188)
<br>> >>> > at
<br>> >>> > java.util.concurrent.ThreadPoolExecutor.runWorker(
<br>> >>> > ThreadPoolExecutor.java:1149)
<br>> >>> > at
<br>> >>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
<br>> >>> > ThreadPoolExecutor.java:624)
<br>> >>> > at java.lang.Thread.run(Thread.java:748)
<br>> >>> >
<br>> >>> >
<br>> >>> > I'm scratching my head as to the cause of this. It's like it is
<br>> trying
<br>> >>> to
<br>> >>> > deleteById for the value "]", even though that is not the ID for
<br>> >>> > the document that was deleted from the primary. So I don't know
<br>> >>> > if it is pulling this from the wrong field somehow or where that
<br>> >>> > value if
<br>> coming
<br>> >>> > from.
<br>> >>> >
<br>> >>> > I found this issue:
<br>> >>> > <a href="https://issues.apache.org/jira/browse/SOLR-9394">https://issues.apache.org/jira/browse/SOLR-9394</a>
<br>> >>> which
<br>> >>> > looks related, but doesn't look like it has any traction.
<br>> >>> >
<br>> >>> > Has anyone else experienced this issue with CDCR, or have any
<br>> >>> > ideas
<br>> as
<br>> >>> to
<br>> >>> > what could be causing this issue?
<br>> >>> >
<br>> >>> > Thanks,
<br>> >>> >
<br>> >>> > Chris
<br>> >>> >
<br>> >>>
<br>> >>
<br>> >>
<br>> >
<br>>Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0tag:blogger.com,1999:blog-1950344992665844384.post-9334764048691275782018-04-01T22:50:00.005-07:002018-04-01T22:51:11.199-07:00FW: Question liste solr-----Original Message-----
<br>From: Rahul Singh [mailto:<a href="mailto:rahul.xavier.singh@gmail.com">rahul.xavier.singh@gmail.com</a>]
<br>Sent: 20 March 2018 20:10
<br>To: <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>; <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>Subject: RE: Question liste solr
<br>
<br>Parallel processing in any way will help, including Spark w/ a DFS like S3
<br>or HDFS. Your three machines could end up being a bottleneck and you may
<br>need more nodes.
<br>
<br>On Mar 20, 2018, 2:36 AM -0500, LOPEZ-CORTES Mariano-ext
<br><<a href="mailto:mariano.lopez-cortes-ext@pole-emploi.fr">mariano.lopez-cortes-ext@pole-emploi.fr</a>>, wrote:
<br>> CSV file is 5GB aprox. for 29 millions.
<br>>
<br>> As you say Christopher, at the beggining we thougth that reading chunk
<br>> by chunk from Oracle and writing to Solr was the best strategy.
<br>>
<br>> But, from our tests we've remarked:
<br>>
<br>> CSV creation via PL/SQL is really really fast. 40 minutes for the full
<br>dataset (with bulk collect).
<br>> Multiple SELECT calls from java slows down the process. I think Oracle is
<br>the bottleneck here.
<br>>
<br>> Any other ideas/alternatives?
<br>>
<br>> Some other points to remark:
<br>>
<br>> We are going to enable autoCommit for every 10 minutes / 10000 rows. No
<br>commit from client.
<br>> During indexing, whe call all the time a front-end load-balancer that
<br>redirect calls to the 3-node cluster.
<br>>
<br>> Thanks in advance!!
<br>>
<br>> ==>Great maillist and really awesome tool!!
<br>>
<br>> -----Message d'origine-----
<br>> De : Christopher Schultz [mailto:<a href="mailto:chris@christopherschultz.net">chris@christopherschultz.net</a>]
<br>> Envoyé : lundi 19 mars 2018 18:05
<br>> À : <a href="mailto:solr-user@lucene.apache.org">solr-user@lucene.apache.org</a>
<br>> Objet : Re: Question liste solr
<br>>
<br>> -----BEGIN PGP SIGNED MESSAGE-----
<br>> Hash: SHA256
<br>>
<br>> Mariano,
<br>>
<br>> On 3/19/18 11:50 AM, LOPEZ-CORTES Mariano-ext wrote:
<br>> > Hello
<br>> >
<br>> > We have an index Solr with 3 nodes, 1 shard et 2 replicas.
<br>> >
<br>> > Our goal is to index 42 millions rows. Indexing time is important.
<br>> > The data source is an oracle database.
<br>> >
<br>> > Our indexing strategy is :
<br>> >
<br>> > * Reading from Oracle to a big CSV file.
<br>> >
<br>> > * Reading from 4 files (big file chunked) and injection via
<br>> > ConcurrentUpdateSolrClient
<br>> >
<br>> > Is it the optimal way of injecting such mass of data into Solr ?
<br>> >
<br>> > For information, estimated time for our solution is 6h.
<br>>
<br>> How big are the CSV files? If most of the time is taken performing the
<br>various SELECT operations, then it's probably a good strategy.
<br>>
<br>> However, you may find that using the disk as a buffer slows everything
<br>down because disk-writes can be very slow.
<br>>
<br>> Why not perform your SELECT(s) and write directly to Solr using one of the
<br>APIs (either a language-specific API, or through the HTTP API)?
<br>>
<br>> Hope that helps,
<br>> - -chris
<br>> -----BEGIN PGP SIGNATURE-----
<br>> Comment: GPGTools - <a href="http://gpgtools.org">http://gpgtools.org</a>
<br>> Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/">http://www.enigmail.net/</a>
<br>>
<br>> iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlqv7aEdHGNocmlzQGNo
<br>> cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFgJrg//RushznZlTg60TxdE
<br>> s/XKK+69s9c0+DwZ/IrU366j2ZOcJl8Osu9TpzaCSEpdWuulFG8qCSYThTngaijH
<br>> I02YCqnK9Ey4+6B7u9QECWNXjdlQXoeINjCnRLVENWzkSmht/U2nW3WTFEPKOvQ3
<br>> 6ISTPATFnfo6Wt4VYrVefqO/yCCiR5bGL5LsSZYwvqlh9egR8K/wtf4sQ5kji3z+
<br>> r2Z0gYpR9igE3ZCIByf6QGq0Ftku90oFCG+kCVNOdgfqwkUaMdc7krv92oTSH4o5
<br>> BH+trc2jPf3HKFmp/ywRAPEhAfA5BwbT8vB9gwl/6vuT6efAot7xrLqduF3h7jG6
<br>> ffPtkEBbD/ld3inIVta6/hnUwxX9O1fBtJrZegD14cezLV9QcEWFJ8/lUfgGOTdX
<br>> ZuvwxBFhmCXE9EMWLlpdUOWK9iVBsZoQZxawoqw9xQauBp/Adg29fdeXmEkUssey
<br>> 85HGDv/x33Bcr1xPGa8nOygWcZRUgGFCh871qStg9GeTNx3C/mSk0wxdKeUDRePg
<br>> GEuL0p803yCJYAddyF66nnx676LfFeDaocBJelx5UbiteNT23xut7jWP/COyOvoy
<br>> tpq3c9UfIkobgcA7bZ3IL2Og+hExgo+tLQXiOx6bf2TD1Jk2UOWWk1TAUspuUybD
<br>> VH6PlwgqcrO28Jx799mJvpIotoE=
<br>> =aMPk
<br>> -----END PGP SIGNATURE-----Anonymoushttp://www.blogger.com/profile/06883891848819037621noreply@blogger.com0