Monday, March 19, 2018

FW: Securying ONLY the web interface console

-----Original Message-----
From: Jesus Olivan [mailto:jesus.olivan@letgo.com]
Sent: 19 March 2018 22:49
To: solr-user@lucene.apache.org
Subject: Securying ONLY the web interface console

hi!

i'm trying to password protect only Solr web interface (not queries launched
from my app). I'm currently using SolrCloud 6.6.0 with external zookeepers.
I've read tons of Docs about it, but i couldn't find a proper way to secure
ONLY the web admin console. Can anybody give me some light about it, please?
=)

Thanks in advance!
Posted by at No comments:

FW: Question liste solr

-----Original Message-----
From: LOPEZ-CORTES Mariano-ext
[mailto:mariano.lopez-cortes-ext@pole-emploi.fr]
Sent: 19 March 2018 21:22
To: 'solr-user@lucene.apache.org' <solr-user@lucene.apache.org>
Subject: RE: Question liste solr

Sorry. Thanks in advance !!

De : LOPEZ-CORTES Mariano-ext
Envoyé : lundi 19 mars 2018 16:50
À : 'solr-user@lucene.apache.org'
Objet : RE: Question liste solr

Hello

We have an index Solr with 3 nodes, 1 shard et 2 replicas.

Our goal is to index 42 millions rows. Indexing time is important. The data
source is an oracle database.

Our indexing strategy is :

· Reading from Oracle to a big CSV file.

· Reading from 4 files (big file chunked) and injection via
ConcurrentUpdateSolrClient

Is it the optimal way of injecting such mass of data into Solr ?

For information, estimated time for our solution is 6h.
Posted by at No comments:

FW: How does group.query work in solr?

-----Original Message-----
From: Anjani Kumar [mailto:anj.2403@gmail.com]
Sent: 19 March 2018 18:38
To: solr-user@lucene.apache.org
Subject: How does group.query work in solr?

I am trying to achieve grouping according to the fields matched in a single
query. So in the group.query parameter I am passing individual queries
according to field names and in the query parameter, I am passing just the
search term to be matched against the default copy fields. However It is
taking too much time compared to querying individual fields separately and
combining the data at my end.

here is the sample query:

http://localhost:8983/solr/psqlTest/select?q=201*&wt=json&indent=true&group=
true&group.query=road_name:201*&group.query=own_name:201*&group.query=tel_no
:201*&group.query=assm_no:201*&group.limit=5


This query takes time in order of seconds to complete when atleast 100 users
are hitting(using jmeter).

The query over each fields and joining the results take time in order of
100-200 ms for the same jmeter parameters. Why is there such a huge
difference in the performance?
Posted by at No comments:

FW: [PHP Classes] Notable PHP package: PHP Screenshot URL Handler

 

 

From: PHP Classes Notable [mailto:list-notable@phpclasses.org]
Sent: 19 March 2018 12:58
To: ROSHAN <roshan@siddhast.com>
Subject: [PHP Classes] Notable PHP package: PHP Screenshot URL Handler

 

Capturing screenshots of Web pages is useful for site developers. It helps understanding how Web site users see their Web site pages. Eventually, that may be useful to discover bugs or issues with the way the pages are presented to the user and that may not be alright. There are many solutions to capture screenshots of Web pages. Using the Google Page Speed API is often better because internally Google uses the Chrome browser to capture exactly the way pages are presented to users, as if there was a real user seeing a given Web page. This package uses Google Page Speed API to capture a Web page screenshot, thus taking advantage of its possibilities as described above.

Notable PHP package: PHP Screenshot URL Handler

Replay Real User Sessions

Monitor and Replay what Real Users do on your Website or Web app

ROSHAN, a PHP package is considered Notable when it does something different that is worth noting.

If you have also written Notable packages, contribute them to the PHP Classes site to get your work more exposure.

If your notable package is innovative, you may also earn prizes and recognition in the PHP Innovation Award.

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: List of prizes

 

Package

PHP Screenshot URL Handler

Manipulate URLs and capture a screenshot of a page

Moderator comment

Capturing screenshots of Web pages is useful for site developers. It helps understanding how Web site users see their Web site pages. Eventually, that may be useful to discover bugs or issues with the way the pages are presented to the user and that may not be alright.

There are many solutions to capture screenshots of Web pages. Using the Google Page Speed API is often better because internally Google uses the Chrome browser to capture exactly the way pages are presented to users, as if there was a real user seeing a given Web page.

This package uses Google Page Speed API to capture a Web page screenshot, thus taking advantage of its possibilities as described above.

Author

Malik umer Farooq

Groups

PHP 5, Web services

Description

This package can manipulate URLs and capture a screenshot of a page.

It can perform several operations with URLs like:

- Cenerate the slug part from a text string
- Retrieve the contents of the respective page
- Extract the page title, meta description, keywords, images
- Capture a screenshot using the Google Page Speed API

 

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 unsubscribe page.

Posted by at No comments:

FW: Error when indexing with SolrJ HTTP ERROR 405

-----Original Message-----
From: Khalid Moustapha Askia [mailto:m.askiakhalid@gmail.com]
Sent: 19 March 2018 09:16
To: solr-user@lucene.apache.org
Subject: Error when indexing with SolrJ HTTP ERROR 405

Hi. I am trying to index some data with Solr by using SolrJ. But I have this
error that I can't solve.

----------------------------------------------------------------------------
---------------------------------
Exception in thread "main"
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at http://localhost:8983/solr/#/corename: Expected mime type
application/octet-stream but got text/html. <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 405 HTTP POST method is not supported by this URL</title>
</head>
<body><h2>HTTP ERROR 405</h2>
<p>Problem accessing /solr/index.html. Reason:
<pre> Error 405 HTTP POST method is not supported by this
URL</pre></p>
</body>
</html>

at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClien
t.java:558)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java
:259)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java
:248)
at
org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:106)
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:71)
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:85)
at indexsolr.index(indexsolr.java:33)
at LoadData.toIndex(LoadData.java:102)
at LoadData.loadDocuments(LoadData.java:72)
at IndexLaunch.main(IndexLaunch.java:12)

----------------------------------------------------------------------------
------------------------------

This is how I connect (I am in local):

--------------------------------------------------------------------

SolrClient client = new HttpSolrClient.Builder("
http://localhost:8983/solr/#/corename").build();

When I remove the "#" It throws a NullPointerException

I have been struggling for a week with this indexing...
Posted by at No comments:

Sunday, March 18, 2018

FW: Indexing multi level Nested JSON

-----Original Message-----
From: Zheng Lin Edwin Yeo [mailto:edwinyeozl@gmail.com]
Sent: 19 March 2018 08:46
To: solr-user@lucene.apache.org
Subject: Indexing multi level Nested JSON

Hi,

I have this sample multi level Nested JSON, with 2 level of child Documents.

[
{
"id": "1",
"title_s": "Solr adds block join support",
"contenttype_s": "parentDocument",
"_childDocuments_": [
{
"id": "3",
"comments_s": "SolrCloud supports it too!",
"_childDocuments_":[{"name_s":"alan","phone_s":"123"},{"name_s":"edwin","pho
ne_s":"456"}]
},
{
"id": "3a",
"comments_s": "SolrCloud supports it too 2!",
"_childDocuments_":[{"name_s":"alan","phone_s":"123"},{"name_s":"edwin","pho
ne_s":"456"}]
}
]
},
{
"id": "2",
"title_s": "New Lucene and Solr release is out",
"contenttype_s": "parentDocument",
"_childDocuments_": [
{
"id": "4",
"comments_s": "Lots of new features",
"_childDocuments_":[{"name_s":"alan","phone_s":"123"},{"name_s":"edwin","pho
ne_s":"456"}]
}
]
},
{
"id": "5",
"title_s": "Testing of Nested JSON",
"contenttype_s": "parentDocument",
"_childDocuments_": [
{
"id": "6",
"comments_s": "See if this is a child",
"_childDocuments_":[{"name_s":"alan","phone_s":"123"},{"name_s":"edwin","pho
ne_s":"456"}]
}
]
}
]


However, when it is indexed into Solr, there is only one level, and the
output becomes like this.

{
"responseHeader":{
"zkConnected":true,
"status":0,
"QTime":1,
"params":{
"q":"contenttype_s:parentDocument",
"fl":"*,[child parentFilter=contenttype_s:parentDocument]",
"sort":"id asc"}},
"response":{"numFound":3,"start":0,"docs":[
{
"id":"1",
"title_s":"Solr adds block join support",
"contenttype_s":"parentDocument",
"signature":"0000000000000000",
"_version_":1595334082096529408,
"_childDocuments_":[
{
"name_s":"alan",
"phone_s":"123",
"_version_":1595334082096529408},
{
"name_s":"edwin",
"phone_s":"456",
"_version_":1595334082096529408},
{
"id":"3",
"comments_s":"SolrCloud supports it too!",
"_version_":1595334082096529408},
{
"name_s":"alan",
"phone_s":"123",
"_version_":1595334082096529408},
{
"name_s":"edwin",
"phone_s":"456",
"_version_":1595334082096529408},
{
"id":"3a",
"comments_s":"SolrCloud supports it too 2!",
"_version_":1595334082096529408}]},
{
"id":"2",
"title_s":"New Lucene and Solr release is out",
"contenttype_s":"parentDocument",
"signature":"0000000000000000",
"_version_":1595334082099675136,
"_childDocuments_":[
{
"name_s":"alan",
"phone_s":"123",
"_version_":1595334082099675136},
{
"name_s":"edwin",
"phone_s":"456",
"_version_":1595334082099675136},
{
"id":"4",
"comments_s":"Lots of new features",
"_version_":1595334082099675136}]},
{
"id":"5",
"title_s":"Testing of Nested JSON",
"contenttype_s":"parentDocument",
"signature":"0000000000000000",
"_version_":1595334082101772288,
"_childDocuments_":[
{
"name_s":"alan",
"phone_s":"123",
"_version_":1595334082101772288},
{
"name_s":"edwin",
"phone_s":"456",
"_version_":1595334082101772288},
{
"id":"6",
"comments_s":"See if this is a child",
"_version_":1595334082101772288}]}]
}}


Is Solr able to support the indexing of multi level Nested JSON?

I have tested this on Solr 6.5.1.

Regards,
Edwin
Posted by at No comments:

FW: [aadhaarauth] Auth Url not working

 

 

From: contact.manishkangia via Aadhaar Authentication Discussions Group [mailto:aadhaarauth+APn2wQfAd3P8GX6nKi2pUMIuSXMdc3Q2iJPInXs4W3Q6GIcvDGlL@googlegroups.com]
Sent: 19 March 2018 00:09
To: Aadhaar Authentication Discussions Group <aadhaarauth@googlegroups.com>
Subject: [aadhaarauth] Auth Url not working

 

Hi,


Following the details here https://authportal.uidai.gov.in/web/uidai/developer to test aadhar authentication.


i am trying to ping for authentication at http://auth.uidai.gov.in/1.6//<1st-digit-of-uid>/<2nd-digit-of-uid>/ but it's not able to connect.


I tried the url that use to worker earlier
http://auth.uidai.gov.in/1.6/public/9/9/MEaMX8fkRa6PqsqK6wGMrEXcXFl_oXHA-YuknI2uf0gKgZ80HaZgG3A

 

and also tried without "public"
http://auth.uidai.gov.in/1.6/9/9/MEaMX8fkRa6PqsqK6wGMrEXcXFl_oXHA-YuknI2uf0gKgZ80HaZgG3A


Is the service unavailable or has been moved to a different url?


Please help with this.


Regards

--
--
********* USAGE GUIDELINES AND DISCLAIMER *********
https://groups.google.com/forum/#!forum/aadhaarauth
 
Please consider the environment before printing or forwarding.
 
All participants on this discussion group are advised not to share confidential content. This email may contain virus or malware. You are advised to take necessary protection. UIDAI does not guarantee the reliability, completeness, accuracy, timeliness or up-to-date-ness of the material presented here or take any liability on any damage caused by using the content. In your use of the forum, you agree that you will not post any information which is unlawful, harmful, threatening, abusive, harassing, defamatory, vulgar, obscene, harassing, threatening, invading of others privacy, hateful, racially, ethnically or otherwise objectionable or violates any laws.
 
By using this group, you automatically agree to terms at http://developer.uidai.gov.in/site/group_terms
********* USAGE GUIDELINES AND DISCLAIMER *********
---
You received this message because you are subscribed to the Google Groups "Aadhaar Authentication Discussions Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aadhaarauth+unsubscribe@googlegroups.com.
To post to this group, send email to aadhaarauth@googlegroups.com.
Visit this group at https://groups.google.com/group/aadhaarauth.
For more options, visit https://groups.google.com/d/optout.

Posted by at No comments:
Subscribe to: Posts (Atom)