The way how to fix the error in Solr system - apache

Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused by:
QueryElevationComponent missing config file: 'elevate.xml either:
F:\dev\solr-7.4.0\server\solr\new_core\conf\elevate.xml or F:\dev\solr-7.4.0\server\solr\new_core\data\elevate.xml
must exist, but not both.
Creating the core in Solr, I got this error
Why was it happened?

It's missing the elevate.xml file. You either remove the reference to the file from your configuration (where you have configured the Query Elevation Component, or you add an empty file.

Related

error creating solr core

I got this error:
Error CREATEing SolrCore 'my': Unable to create core [my] Caused by: Input length = 1
I don't have any idea about this error. I am using solr 6.2.1.
I made the collection folder, added solrconfig, schema, data-config file in conf folder, it first gave me an error to add lang/stopwords_it.txt, and after that it showed this error. Please help. I am new to solr.
Under Unix, you could create a new solr core with the following bash-script:
https://github.com/patrick0585/Solr-Core-Creator
./solr_core_creator.sh --core --conf --lib

ClickOnce running an error when publishing Application

whenever I try to publish my application and it gives me this error:
Failed to connect to '\localhost\users\Dylan Garcia\Desktop\8.2.1_File\' with the following error: unable to create the Web site '\localhost\users\Dylan Garcia\Desktop\8.2.1_File\'. The path '\localhost\users\Dylan Garcia\Desktop\8.2.1_File\' does not exist or you do not have access. The specified path is invalid.
how could i resolve this issue?
Hope you have already fixed this error.
First make sure that you have created the folder 8.2.1_File on your desktop, then try either one of the following
\\\localhost\users\Dylan Garcia\Desktop\8.2.1_File\
or
C:\users\Dylan Garcia\Desktop\8.2.1_File\

Solr is not going to configure

In drupal 7, website I am using search API, and trying to index data, getting error
An error occurred while trying to retrieve additional information from the Solr server: "500" Status: PWC6033: Unable to compile class for JSP PWC6197: An error occurred at line: 41 in the jsp file: /admin/stats.jsp PWC6199: Generated servlet error: The type java.util.Map$Entry cannot be resolved. It is indirectly referenced from required .class files org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP PWC6197: An error occurred at line: 41 in the jsp file: /admin/stats.jsp PWC6199: Generated servlet error: The type java.util.Map$Entry cannot be resolved. It is indirectly referenced from required .class files at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:123) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:296) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:376) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:437) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:360) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
Granted I am using ApacheSolr rather than Search API, but I think this issue may not be Drupal module dependent. I had this problem locally when trying to use either Solr 3.5.0 or Solr 3.6.2 on my mac. When I switched to using Solr 4.9.1 this issue went away. I downloaded Solr 4.9.1, and placed it outside the root of my drupal install. I then copied the files from
[my-site]/sites/all/modules/contrib/apachesolr/solr-conf/solr-4.x to [wherever you put the solr download]/solr-4.9.1/example/solr/collection1/conf (the file structure for the conf files looks different for solr 4 and solr 3). Then start solr as usual - from within solr-4.9.1/example run java -jar java.jar

Adding Files view on Ambari 1.7.0: ClassNotFoundException

I'm trying to add views on Ambari 1.7.0.
For the Files view that is available here: https://github.com/apache/ambari/tree/trunk/contrib/views/files
I get an error after trying to launch an instance of the view:
500 HdfsApi connection failed. Check "webhdfs.url" property
With the following Stack Trace (just the first lines):
java.lang.RuntimeException: java.lang.ClassNotFoundException: Class org.apache.hadoop.hdfs.web.WebHdfsFileSystem not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1720)
at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:2415)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2428)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:88)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2467)
I just add the following property during the configuration of the view:
webhdfs.url webhdfs://mycluster1:50070
I'm not sure but perhaps it's an issue during the building part like version conflict, i'm working on that.
Any ideas?
What is the value you have used for WebHDFS url in file view instance ?
Is your cluster Namenode HA enabled ? If yes , try to use url as webhdfs://:50070
If not HA enabled the use webhdfs://:50070
If none works use direct data node dfs address as webhdfs://:50070

MonoDevelop and AjaxControlToolkit: Register Server Tag in Mono

I know that Mono supports the AjaxControlToolkit but I don't know how to integrate it into MonoDevelop. I added AjaxControlToolkit.dll, System.Web.Extensions.dll and System.Web.Extensions.Design.dll as References in the project but when I build the project I get the warning:
/Users/user1/Projects/FirstProject/Default.aspx(1,1): Warning: Parser failed with error The tag type 'ajaxToolkit:TabContainer' has not been registered.. CodeBehind members for this file will not be added. (FirstProject)
and I when I deploy it I get the error: Unknown server tag 'ajaxToolkit:TabContainer'.
How do I register the server tag in MonoDevelop?
You can use either the <%#Register directive, or add some lines to your Web.config. See here for instructions on either approach.
Using the Web.config mechanism has the advantage that you don't need to add a directive to every page where you want to use the controls.