Skip to main content

Indexing PostgreSQL with Apache Solr

Image
By
Listen:

Searching and filtering large IP address datasets within PostgreSQL can be challenging. Why? Databases excel at data storage and structured queries, but often struggle with full-text search and complex analysis. Apache Solr, a high-performance search engine built on top of Lucene, is designed to handle these tasks with remarkable speed and flexibility.

What do we need?

  • A running PostgreSQL database with a table containing IP address information (named "ip_loc" in our example).
  • A basic installation of Apache Solr.

Setting up Apache Solr

1. Create a Solr Core:

solr create -c ip_data -d /path/to/solr/configsets/

2. Define the Schema (schema.xml)

<field name="start_ip" type="ip" indexed="true" stored="true"/>
<field name="end_ip" type="ip" indexed="true" stored="true"/>
<field name="iso2" type="string" indexed="true" stored="true"/>
<field name="state" type="text_general" indexed="true" stored="true"/>
<field name="city" type="text_general" indexed="true" stored="true"/>

Integrating PostgreSQL and Solr

Solr's DataImportHandler (DIH): Add the following DIH configuration to your solrconfig.xml:

<dataConfig>
    <dataSource type="JdbcDataSource" 
                driver="org.postgresql.Driver"
                url="jdbc:postgresql://localhost/your_database"
                user="your_username" 
                password="your_password"/>
    <document>
        <entity name="ip_data" query="SELECT * FROM ip_loc">
            <field column="start_ip" name="start_ip" /> 
            </entity>
    </document>
</dataConfig>

Import Data: Initiate the data import using the Solr admin interface or the command line:

http://localhost:8983/solr/ip_data/dataimport?command=full-import

Querying Solr

  • IP Range Search: start_ip:[192.168.0.1 TO 192.168.255.255]
  • Geolocation Filtering: iso2:US AND state:California
  • Combined Search: city:NewYork AND start_ip:[10.0.0.0 TO 10.255.255.255]

Benefits vs. Pure PostgreSQL

  1. Performance: Solr's inverted indexes provide superior search speed.
  2. Scalability: Solr easily distributes across multiple machines.
  3. Flexibility: Solr's query syntax offers rich search capabilities.

My take

By combining PostgreSQL and Apache Solr, you create a robust IP address management system that scales efficiently while providing lightning-fast search functionality.

Labels:

Comments

Post a Comment

Popular posts from this blog

Beyond Ctrl+F - Use LLM's For PDF Analysis

By
PDFs are everywhere, seemingly indestructible, and present in our daily lives at all thinkable and unthinkable positions. We've all got mountains of them, and even companies shouting about "digital transformation" haven't managed to escape their clutches. Now, I'm a product guy, not a document management guru. But I started thinking: if PDFs are omnipresent in our existence, why not throw some cutting-edge AI at the problem? Maybe Large Language Models (LLMs) and Retrieval Augmented Generation (RAG) could be the answer. Don't get me wrong, PDF search indexes like Solr exist, but they're basically glorified Ctrl+F. They point you to the right file, but don't actually help you understand what's in it. And sure, Microsoft Fabric's got some fancy PDF Q&A stuff, but it's a complex beast with a hefty price tag. That's why I decided to experiment with LLMs and RAG. My idea? An intelligent knowledge base built on top of our existing P...
Post a Comment
Read more

Deal with corrupted messages in Apache Kafka

By
Under some strange circumstances, it can happen that a message in a Kafka topic is corrupted. This often happens when using 3rd party frameworks with Kafka. In addition, Kafka < 0.9 does not have a lock on Log.read() at the consumer read level, but does have a lock on Log.write(). This can lead to a rare race condition as described in KAKFA-2477 [1]. A likely log entry looks like this: ERROR Error processing message, stopping consumer: (kafka.tools.ConsoleConsumer$) kafka.message.InvalidMessageException: Message is corrupt (stored crc = xxxxxxxxxx, computed crc = yyyyyyyyyy Kafka-Tools Kafka stores the offset of each consumer in Zookeeper. To read the offsets, Kafka provides handy tools [2]. But you can also use zkCli.sh, at least to display the consumer and the stored offsets. First we need to find the consumer for a topic (> Kafka 0.9): bin/kafka-consumer-groups.sh --zookeeper management01:2181 --describe --group test Prior to Kafka 0.9, the only way to get this in...
Post a Comment
Read more

What Makes You The Number 1 Product Manager?

By
Amazon often does this thing where they start with the customer instead of just coming up with a product and then trying to figure out how to sell it. They call it " working backwards. " This strategy totally works for any product decisions, but it's especially important when they're making something new. The Press Release Exercise When it comes to launching new stuff, product managers usually start by writing a press release for customers. This press release is all about their pain points, how current solutions fall short, and how the new product is going to crush it. If the benefits don't get customers excited, the product manager needs to keep tweaking the press release until it sounds super awesome. It's way easier and cheaper to make changes to a press release than it is to change the product itself. Here’s a template I use to describe a new service or product: Main heade r: The product name anyone directly understands, like “Ultra-compact power charger” ...
Post a Comment
Read more