SOLR指数减少(SOLR index size reduction)
对于一个大型项目,我们有一些大规模的SOLR索引,并且其消耗的空间超过50 GB。
我们已经考虑了几种缩小与改变指数内容相关的规模的方法,但我很好奇是否可以对SOLR指数做出任何改变,从而将其规模缩小2个数量级或更多,它们与(1)我们可以运行的维护命令或(2)可能没有正确设置的简单配置参数直接相关。
另一个相关的问题是(3)是否有一种方法可以在SOLR内部交易业绩指数大小,如果是,它将如何工作?
任何想法,将不胜感激......谢谢!
We have a some massive SOLR indices for a large project, and its consuming above 50 GB of space .
We have considered several ways to reduce the size that are related to changing the content in the indices, but I am curious of wether or not there might be any changes we can make to a SOLR index which will reduce its size by 2 orders of magnitude or more, which are directly related to either (1) maintainance commands we can run or (2) simple configuration parameters which may not be set right.
Another relevant question is (3) Is there a way to trade index size for performance inside of SOLR, and if so , how would it work ?
Any thoughts on this would be appreciated... Thanks!
原文:https://stackoverflow.com/questions/10080881
最满意答案
不 ,不是因为恶意用户只能访问该URL
www.site.com/domain/product.php?id=123'; DROP TABLE products;
并完全绕过你的mod_rewrite。 虽然只会重写整数,但是要重写它们的URL仍然可用且可访问。 无论何时进行SQL查询,都应使用PDO等清理当前进入查询的每个输入。
No it does not because a malicious user could simply go to the URL
www.site.com/domain/product.php?id=123'; DROP TABLE products;
and bypass your mod_rewrite entirely. Although only integers will be rewritten, the URL that they are being rewritten to use is still live and accessible. Any time you are making an SQL query you should sanitize every input going into your query at that point using PDO etc.
相关问答
更多-
试试这个: RewriteEngine on RewriteRule ^([A-Za-z0-9-]+)$ main.php?user=$1 [NC,L] Try this: RewriteEngine on RewriteRule ^([A-Za-z0-9-]+)$ main.php?user=$1 [NC,L]
-
对于Apache,您可以使用mod_ssl强制使用SSLRequireSSL Directive SSL: 除非针对当前连接启用了HTTP over SSL(即HTTPS),否则此伪指令禁止访问。 这在启用SSL的虚拟主机或目录中非常方便,以防止发生应该受保护的内容的配置错误。 当此指令出现时,所有拒绝使用SSL的请求都被拒绝。 这不会重定向到https。 要重定向,请尝试以下与.htaccess文件中的mod_rewrite RewriteEngine On RewriteCond %{HTTPS} != ...
-
不 ,不是因为恶意用户只能访问该URL www.site.com/domain/product.php?id=123'; DROP TABLE products; 并完全绕过你的mod_rewrite。 虽然只会重写整数,但是要重写它们的URL仍然可用且可访问。 无论何时进行SQL查询,都应使用PDO等清理当前进入查询的每个输入。 No it does not because a malicious user could simply go to the URL www.site.com/domain/p ...
-
我对mod重写并不“很棒”,但你可以创建一个超出普通文件夹结构的代理脚本,并使用PHP来获取这些变量并将其传递回应用程序。 I am not "great" with mod rewrite but you can create a proxy script that is outside your normal folder structures and uses PHP to grab that variables and pass it back up to your application.
-
如果在将数据放入查询之前未正确清理数据,则应始终认为自己容易受到SQL注入攻击。 使用.htaccess重写不是也不应该被视为防止SQL注入的做法。 使用mysql_real_escape_string或pg_escape_string (如果使用PHP)或使用POST或GET变量对所有查询使用pg_escape_string准备语句。 总是。 You should always consider yourself vulnerable to SQL injection attack if you don' ...
-
重写引擎循环,因此当引擎循环时,重写到查询字符串的最后一条规则会被第一条规则捕获。 您需要匹配%{THE_REQUEST}变量,而不是匹配%{QUERY_STRING}变量,以便它不受其他重写的影响:
RewriteEngine On RewriteCond %{THE_REQUEST} /results\.php\?query1=([^&]+)&query2=([^&\ ]+) [NC] RewriteRule ^results. ... -
由于您的网址和文件的名称非常相似,因此与MultiView可能会有一些冲突。 尝试禁用它: Options -MultiViews There might be some conflicts with MultiViews as your URL and files have a very similar name. Try to disable it: Options -MultiViews
-
垂直条表示逻辑OR ,并允许您在“注册”之后指定尾部斜杠。 我更喜欢用'?' 斜线后,使其成为可选: RewriteRule ^registration/?$ /index.php The vertical bar stands for a logical OR, and lets you specify either a trailing slash after 'registration' or not. I prefer using a '?' after the slash, making it ...
-
403在WordPress中使用mod_rewrite时出现Forbidden错误(403 Forbidden error when using mod_rewrite with WordPress)[2022-11-16]
改变这一行: RewriteCond %{QUERY_STRING} ^.*(\[|\]|\(|\)|<|>|ê|"|;|\?|\*|=$).* [NC,OR] 至: RewriteCond %{QUERY_STRING} ^.*(\[|\]|\(|\)|<|>|ê|"|;|\?|\*).* [NC,OR] Change this line: RewriteCond %{QUERY_STRING} ^.*(\[|\]|\(|\)|<|>|ê|"|;|\?|\*|=$).* [NC,OR] to: Re ... -
如何正确mod_rewrite(how to properly mod_rewrite)[2022-03-23]
你的第一套规则: #redirect domain.com to www.domain.com RewriteCond %{HTTP_HOST} !^www\.domain\.com$ [NC] RewriteRule .+ http://www.domain.com%{REQUEST_URI} [R=301,NC] 如果您没有空请求,则取代您拥有的任何子域。 第二套规则接近你想要的。 但是它们循环并且它们不会将多个子域条目转换为目录路径,因此请首先尝试使用这组规则: # Prevent looping ...